Using scripting languages for KDE4 main modules

Simon Edwards simon at
Thu Sep 28 18:48:27 BST 2006

On Thursday 28 September 2006 17:44, Adriaan de Groot wrote:
> On Thursday 28 September 2006 17:39, Dirk Mueller wrote:
> > On Thursday, 28. September 2006 16:07, Albert Astals Cid wrote:
> > > Both at the kdegames BOF and kdeedu BOF there was discussion about if
> > > programs created enterely in Ruby/Python/etc are going to be allowed to
> > > be in main modules of kde for KDE 4.
> >
> > The TWG actually thinks about requiring that at least one central
> > application in KDE 4 is not written in C++. But this is not finally 
> > yet. So if you can provide one, we'd be more than happy to take it. So a
> > clear "yes"
> Guidance? Some of the power manager stuff? The digital signage app 
> demonstrated here at aKademy?

Well, I'm more or less planning to port the Guidance stuff over to KDE4 
sometime in the not too distant future... Does that count as a central 

> This would produce an interesting addition to the dependency chain, though: 
> working bindings before some of the other modules.

Funny you should mention that. We on the PyKDE list have been discussing that 
a bit in the last few weeks. The idea of developing PyKDE[1] in KDE's SVN and 
releasing up-to-date bindings synchonised with KDE, was positively received. 
Some details needs to be worked out, but it looks like it is going to happen.

Developing a Python application/utility on alpha/beta quality bindings and KDE 
libraries makes things trickier, but in a way it is the same problem that 
every KDE4 application developer faces at the moment.

[1] Another part of the equation is SIP (=bindings tool) and PyQt. PyQt is, 
and will remain developed externally by Riverbank Computing. Newly updated 
versions of PyQt quickly follow any new Qt releases. PyQt is not expected to 
be dependancy/scheduling problem.


Simon Edwards             | KDE-NL, Guidance tools, Guarddog Firewall
simon at       |
Nijmegen, The Netherlands | "ZooTV? You made the right choice."

More information about the kde-core-devel mailing list