Question about C++ vs. Python/Ruby/JS plasmoids

Aaron J. Seigo aseigo at
Wed Aug 27 18:38:05 CEST 2008

On Wednesday 27 August 2008, Paul B wrote:
> On Wednesday 27 August 2008 07:07:50 Arne Babenhauserheide wrote:
> > I have one real-world benefit: Because I can (as of now) only write
> > meaningful stuff in any workable time-frame using Python.
> Main benefit I can think of is that when the plasmoids are scripted and
> don't need to be compiled you can add them straight from the internet using
> the "Add Widgets..." dialog, into your home directory. I don't think that
> counts as "I prefer Python".

this is a feature also provided by ECMA Script. the question is "why $LANG" 
instead of just stickign to ECMA Script.

the reasons i see are:

* you know $LANG, or the project your are integrating with is written in $LANG

* in the cases you need access to more system libraries, but don't want to 
write in C++ (Ruby/Python have bindings for pretty much everything)

so i see real value in these bindings, but i'd hope we can also keep mostly 
focussed on ECMA Script within the default applet set..

that said, it would be wise to have at lest one fun applet for each 
ScriptEngine so that we have a way to monitor for regressions and something 
for other people to look at.

Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : 

More information about the Plasma-devel mailing list