scripting proposal draft 3

[Peter Zhou]

On Wed, Apr 9, 2008 at 11:15 PM, Miguel Angel Alvarez <maacruz at gmail.com>
wrote:

>
> >A script is just a command fed by stdin, which can communicate with
> amarok via
> >dcop/dbus to change it's behaviour, so no way the script can cause any
> >instability in amarok which is not a quality problem of amarok itself
> (except
> >DOS attacks)
> > Since it is nothing more and nothing less than that, it can do anything
> that
> > any command run in the same user account can do, and that's all. Users
> are
> > able to install and run anything, so there are no more security
> implications
> > than anything else the user can do. If the user is afraid of what a
> script
> > can do, he may be able to run amarok under a different user account (the
> same
> > applies to web browsers).
>

Using Kross will cause some stability problems. It can let the scripts to
use the UI pointers directly.
So, I am planning to propose a list of functions/pointers to use kross, and
to leave other classes/functions to continue using dbus.

Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20080410/2b9b79ef/attachment.html>