[Openicc] KDE CMS [was: List Scope]

[Cyrille Berger]

On Tuesday 29 January 2008, you wrote:
> The upside is KDE would get flexible dialogs.
> After all, I a bit surprised to imagine a configuration system like
> kcontrol and no abstraction from widgets. Or does the automation happen
> inside the moc files?
>
> The problem is like with some fancy modules. The user shall set something
> in a dialog for it, options for various screensavers.
> As this option is not always usefull it is provided by API.
> Now I would hope the kcontrol GUI to display that stuff, of course
> with some name or a small logo to understand where it comes from.
We are getting a little bit off-topic for this list, but well :) 
Don't worry if there is a remote chance that a single person will use the 
option, it's available in the GUI ;p That said there is nothing automatic to 
build a GUI from an API, or a list of Key/Values. But there is some 
automation to connect from a hand-made widgets to the KDE Config backend.

> But probably there are very static parts like the Oyranos policies, which
> might get a kcontrol page. It is just a choice.
> The lots of other settings can be placed into a own dialog window or an
> external (Qt?) app?

The goal in KDE4 is to make SystemSettings (the replacement of KControl) the 
*central* place for settings of your computer, and not limited to KDE 
settings. That means, that in the future, distribution settings will be 
available in SystemSettings, that's more or less a merge of KDE3's KControl 
with YaST, Guidance or whatever your distribution use. In short, for ICC 
settings, that mean all settings should be available through system settings.

-- 
Cyrille Berger