To view parent comment, click here.
To read all comments associated with this story, please click here.
I think you missed my point.
The lack of a gconf dependency means that I, as a KDE user
That lack of gconf dependency is a good thing, but why not keep it for GNOME users? An alternative KDE configuration plugin has always been on the TODO list.
Besides, if gconf-editor isn't meant as a config utility, why wouldn't they seperate the config into something less agnostic that could have a proper config utility written around it?
You can just as well write a proper configuration utility using the gconf settings. In fact, that's the whole point. Gconf is not about the UI but about management (lockdown for example) and easier development. gconf-editor is just a convenience tool for developers and geeks who want to access the settings database directly.





Member since:
2005-07-13
That doesn't make a lot of sense... gconf-editor is not meant as a configuration utility for users.
...
What I don't really understand is why they had to drop gconf to support csm, I thought the plan always was to support multiple configuration plugins.
The lack of a gconf dependency means that I, as a KDE user, can run compiz-quinn without requiring the Gnome DE to be installed alongside it. I'm not saying that was the intent, but I'm grateful for it none the less. Seems a little ridiculous to download a DE to use a "desktop agnostic" window manager.
Besides, if gconf-editor isn't meant as a config utility, why wouldn't they seperate the config into something less agnostic that could have a proper config utility written around it?