Plasma desktop init scripting

[Aaron J. Seigo]

On Monday, January 3, 2011, Jeremiah Summers wrote:
>           Thanks, I just realized how unclearly I was thinking. Of course
> this is just for plasma so defaults in KDE apps they may need to be set,
> can't be set. However is there a way to call kwriteconfig in the javascript
> and write to configs on startup?

there isn't currently, no. do you have specific use cases, or just a general 
need/hope?

(creating API to allow reading/writing arbitrary config files would not be 
hard; but use cases help determine if an addition is worth doing.)

> I thought before that some
> things would require a relaunching of the application, is this still the
> case, does it depend on the application etc..?

it depends on the application, yes. this is one of the reasons we opted for 
in-application scripting for plasma: no restarts.

> If I understand you
> correctly then JavaScript can't remove files etc..

only because we don't let it. if there was a sensible set of file cleaning / 
removal services needed, we could provide them in the API. due to the control 
we have over the runtime, we could make this optional depending on script 
trust and ensure that only certain kinds of files are accessible.

> So the bash script in
> env (in my case) will always be needed as it offers more flexibility.

yes, there will always be cases where a "full powered" solution is the most 
direct and useful route. different tools for different jobs :)

-- 
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 Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20110103/f537d0df/attachment.sig