[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Using scripting languages for KDE4 main modules
From:       Richard_Dale () tipitina ! demon ! co ! uk
Date:       2006-10-03 18:03:30
Message-ID: 200610031903.30827.Richard_Dale () tipitina ! demon ! co ! uk
[Download RAW message or body]

On Tuesday 03 October 2006 18:51, Matt Newell wrote:
> On Tuesday 03 October 2006 06:58, Richard_Dale@tipitina.demon.co.uk wrote:
> > On Tuesday 03 October 2006 14:29, Luciano Montanaro wrote:
> > > On Sunday 01 October 2006 20:40, Stephen Leaf wrote:
> > > > On Sunday 01 October 2006 7:31 am, Guillaume Laurent wrote:
> > > > > On Sunday 01 October 2006 13:00, Alexander Neundorf wrote:
> > > > > > I don't think it would be possible to reach a consensus on this
> > > > > > one: python <-> ruby <-> java <-> c# ...
> > > > >
> > > > > We want a script language, so Java and C# are out of consideration,
> > > > > the added value compared to C++ just isn't worth it. So it's
> > > > > between Python and Ruby (at least we all agree that Perl is a no-go
> > > > > :-) ).
> > > >
> > > > not everyone, I hate the python syntax. And as for ruby syntax?..
> > > > I've seen scribbles that were more readable. Maybe it was just the
> > > > examples on the official page I dunno but it just churned my stomach.
> > > > I personally prefer Perl out of those 3 choices.
> > >
> > > What is the state of Perl bindings?
> >
> > There is no work going into the Qt4 version of PerlQt, although it
> > wouln't take a huge amount of effort to adapt the Qt4 QtRuby bindings.
>
> I have the old perlqt bindings working for qt4.  Signals and slots work,
> but only a small portion of the classes are wrapped, and all the
> auto-figure-out-what-features-your-qt-has is ripped out.  So it would still
> require a lot of work to get them up to release quality, and I HATE perl,
> so I'm not going to work on them.
>
> But if there is interest i will send a tarball that could really get
> someone started.  Btw, i have them building on windows too with only mingw,
> perl, and qt as dependancies.
Oh, that's interesting. Do mean the Qt2 PerlQt bindings that were driven 
by .pig interface files, and not the Smoke based Qt3 one? All those .pig 
files were a real pain to get working.

I was talking about updating the Smoke based PerlQt not the older one. The 
slots/signals code in QtRuby would be pretty much identical for Qt3 PerlQt, 
and a lot of other things could be borrowed as QtRuby was based on QtPerl in 
the first place. But working with perlguts and .XS is such a nightmare 
compared with Ruby's C interface, it just isn't something I personally would 
want to contemplate. Although I'd be happy to help someone understand the 
QtRuby code for the port.

-- Richard
[prev in list] [next in list] [prev in thread] [next in thread]