Linked by Thom Holwerda on Tue 19th Sep 2006 15:07 UTC, submitted by SEJeff
X11, Window Managers Just when you thought fancy effects on Linux desktops started to get remotely understandable, focussing on Aiglx/Xgl with Compiz, a fork of Compiz is announced: Beryl. This is the logical continuation of the popular compiz-quinnstorm branch, used by many Ubuntu users. "During this summer, and during the last few weeks, some major additions were done in compiz-quinnstorm, bringing a whole new decorator, cgwd, which was designed to be fully themable, and a new settings backend, csm, which intended to drop most of the gnome deps - there were other reasons for this, but this is not our current subject. Consequently, we reached a situation where it's quite impossible to come back." The main reason is general unwillingness to work with and unresponsiveness to the developers of the -quinnstorm branch from the official Compiz guys.
Thread beginning with comment 163646
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Always hated gconf
by Daniel Borgmann on Tue 19th Sep 2006 17:48 UTC in reply to "Always hated gconf"
Daniel Borgmann
Member since:
2005-07-08

That doesn't make a lot of sense... gconf-editor is not meant as a configuration utility for users. The only reason you _had_ to use it, is that things are still very much work in progress and experimental. As a user interface, I find the CSM utility even more horrible to be honest. 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.

Reply Parent Score: 2

RE[2]: Always hated gconf
by elsewhere on Tue 19th Sep 2006 18:04 in reply to "RE: Always hated gconf"
elsewhere 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?

Reply Parent Score: 3

RE[3]: Always hated gconf
by Daniel Borgmann on Tue 19th Sep 2006 18:16 in reply to "RE[2]: Always hated gconf"
Daniel Borgmann Member since:
2005-07-08

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.

Reply Parent Score: 2