JS Scriptengine in libplasma

[Richard Dale]

On Wed, May 6, 2009 at 8:59 PM, Leonardo Franchi <lfranchi at kde.org> wrote:
> hola folks,
>
> so i'm (finally) looking into adding scripted applet/dataengine support to
> amarok. it's really easy and transparent and all of that (yay plasma!) but we
> have a minor issue. we depend only on kdelibs, and the scriptengines are in
> kdebase/workspace.
>
> i understand that most of them have external deps, which may be undesirable.
> Indeed, we'll most likely restrict all applets/engines to being javascript, so
> as to not require the user to install random *-bindings package. But moving
> the javascript dataengine to the plasma in  kdelibs would really be nice.
I agree that the python and ruby script engine bindings have more
dependency problems than QScript bindings, and it wouldn't make sense
to put them in kdelibs.

However, on the other hand, the python and ruby ones are not really
equivalent to the QScript bindings in kdebase as they pretty much
cover the entire C++ Plasma Applet api, whereas the QScript one covers
a simpler minimal api. At one time, in the kde playground module,
there was work going on into developing some more complete JavaScript
bindings based on the QtJambi parser/code generator. So I wonder if
anyone is intending to develop the more complex bindings further? Have
we had enough feedback yet to know whether or not the simpler bindings
are sufficient for what most people want to do?

-- Richard