Guts of active-settings

[Lamarque V. Souza]

Em Wednesday 21 December 2011, Marco Martin escreveu:
> On Tuesday 20 December 2011, Sebastian Kügler wrote:
> > It would also be cool, if we had an easy way to offer this kind of
> > functionality to apps (so one can, in pure QML) write a configuration
> > interface for ones app -- either by starting active-settings
> > org.kde.active.settings.mycoolapp, or by embedding it somehow. (The
> > former of course needing a mechanism to sync config across processes.
> > Specific modules can be opened right away, by using the plugin name of
> > module as argument to active-settings, much like kcmshell4. (It
> > currently lacks the --list argument, though.)
> 
> from one side i would really like applications config listed in the setting
> app.
> on the other hand, this can end up very quickly as a giant list.
> 
> in any case yeah if the module itself can be loaded as a plugin anywhere,
> we will be able to both display it in the app or in the config app.
> 
> for the config changes across process, don't see other solution than a file
> watcher, that is not so light, but shouldn't be as impactful as it seems
> anyways

	KGlobalSettings::settingsChanged signal works across processes. I am 
using it in these patches http://git.reviewboard.kde.org/r/103434 and 
https://git.reviewboard.kde.org/r/103469/. The only drawback I see in 
KGlobalSettings::SettingsChanged is that is uses an enum to indicatte which 
setting category has changed. That is not that flexible if we need to add new 
categories, like I did when I created the LOCALE category. What is neat with 
this approach is that it automatically reparses the configuration files before 
delivering the signal to the slot.

-- 
Lamarque V. Souza
KDE's Network Management maintainer
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/active/attachments/20111221/b04784f2/attachment-0001.html>