External apps and theme change

[Aaron J. Seigo]

On Thursday 22 January 2009, Ivan Čukić wrote:
> The manager could be fixed to the plasma binary since it is, at the moment,

this is probably the most sensible place for such a thing without creating a 
kded module for it.

> the only place where you can change the theme, but that could prove to be a
> bad solution (IIRC plasma-mid is a separate binary and it should have the
> configuration options for theme) and maybe someone wants to use other
> plasma- based apps without plasma the shell.

well, another thing i considered was putting a KDirWatch on the config file in 
Plasma::Theme and re-reading it when it changes.

there are a few unfortunate things about this, such as taking up a few watch 
handles for a fairly trivial use case and, probably more importantly, re-
reading the config file a lot more than necessary as plasmarc can get saved 
out with modifications a lot more often than the theme is changed.

it might make sense to have a separate file for "plasma enabled apps global 
settings" such as the theme (a small kconfig update script could migrate the 
settings easily) ... or maybe that's a pre-optimization.

in any case, i think the config file change reaction is probably the simplest 
and most foolproof mechanism in this case.

-- 
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 Software

-------------- 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 : http://mail.kde.org/pipermail/plasma-devel/attachments/20090122/58408497/attachment.sig