proposal for full application scripting language in KDE 4

Zack Rusin zack at
Sun Oct 8 16:50:44 BST 2006

On 10/8/06, Scott Wheeler <wheeler at> wrote:

> "So while we want to support non-C++ development, we want one excellent
> binding and I doubt we'll get one excellent one if we don't concentrate on
> one in the core. That doesn't mean other bindings will stop to exist."
> "The TWG actually thinks about requiring that at least one central
> application
> in KDE 4 is not written in C++."
> So how do you decide between them?

We don't. We let the solution naturally evolve. Just like we did with cd
burners back in the day. How many  big non-C++ KDE applications have you
written? How many has everyone in this thread written? How many do we have?
In each case the number is too small to form any reasonable decision. Just
let it be. The two points you quoted above are it. At this point and time
there's nothing more to them. We would like one core binding, period. We
would like at least one central KDE application written in it, period.

We have great infrastructure in place for Python, Ruby, JavaScript and with
QtJambi Java. Once one of those communities will produce a real application,
written from scratch within their respective framework, we'll have a clear
winner. Until then this is just another silly flamewar.

graphics ninja
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the kde-core-devel mailing list