Using scripting languages for KDE4 main modules

Jonas Bähr jonas.baehr at
Sat Oct 7 22:08:51 BST 2006

Am Samstag, 7. Oktober 2006 22:09 schrieb Aaron J. Seigo:
> and this is my concern: we'll end up with 8 different choices in 8
> different apps due to the author's personal preferences or feelings on what
> a user is and should be capable of doing.

Speaking as an application developer here I doubt that this will happen if KDE 
provides good libs for adding scripting to an application. Currently there is 
kjsembed and kross. So a developer has the choice: Either implement a 
complete new binding for his own application and dig throu the extension API 
of this prefered scripting language or he is using one of this libs. As I 
can't realy imagine anyone who prefers the first way we will end up in 
applications that will either depend on kjsembed or kross. The chances that 
each application has bindings for a different language is in my eyes very, 
very low. So, I think the question is not about an official statement of 
which language to use for application scripting but rather to promote 
kjsembed and (not or!) kross and provide decent docs and tutorials for them. 
In this case the problem will solve itself.


Try Krusader... - twinpanel filemanager for KDE

More information about the kde-core-devel mailing list