RFC: plasma2 and configuration

[Marco Martin]

Hi all,

one bit where plasma2 will be very different, even from qml1 applets is how 
configuration dialogs are handled.
Configuraton dialogs will be completely QML based as well.

handling of configuration itself, both reading and writing will be more 
"declarative": an object with properties corresponding to config keys instead 
of  the imperative plamoid.writeConfig()/plasmoid.readConfig()

Now, what is already there right now:
applets have a "configure" entry as a right mouse button action, just as in 
plasma1 and a new window is opened that loads a qml file from the shell 
package.
this contains the "outside" of the configuration dialog: the list of the 
categories and ok/apply/cancel buttons (looks very ugly right now, but will 
end up using desktop components)

this "outside" loads a qml file from the applet plasmoid, at the moment fixed 
as "ConfigGeneral.qml"

it will end up loading all the config pages the plasmoid will offer., i was 
thinking about the following changes:
* everything regarding configuration uis goes away from libplasma
* the plasmoid may offer in their config directory a list of desktop files, 
one per category, that would tell the name of the category, icon, kconfiggroup 
and qml file to load
* All configuration for applets based upon ConfigLoader, only one config.xml 
per plasmoid, supporting multiple config groups
* one config group per page
* eventual extra config pages, like global shortcuts will be provided by the 
shell package, because is not something applets should directly care about

It's still a bit nebulous, want to get this as clear as possible ;)

any comment/idea?

Cheers,
Marco Martin