
That is sort of the point of gconf. A single point of clutter, rather than cluttering other areas of the desktop - especially application menus and preferences.Nylle wrote:Also I find gconf cluttered already, and what's to stop it from becoming more cluttered as the sets of apps supporting it grows. Is it generated dynimcally, or will settings from a program that has been removed live on? In that case it won't be long before it gets very cluttered.

Not at all.Nylle wrote:Something I don't like about the windows registry is that it introduces a single point of failure. If my windows registry gets corrupted, all my settings are gone. Gconf seems to introduce a similar single point of failure, and that concerns me.
Uhm, Actually, the windows registry isn't an .ini file. It's a properitary format that has changed several times in between Windows versions even. If you want more details, see http://www.csdn.net/Dev/Format/binary/WinReg.htmkerrick wrote: Besides, using ini files is more like the Windows registry considering the windows registry is a *#%@ing ini file.
Indeed. Both desktops do a certain inheriting of Windows behavior. KDE does more inheriting than GNOME IMHO. It just inherits better partskerrick wrote:If you really feel the need to compare something to Windows, lets compare Gnome to KDE to Windows and see which one is more like it.
Opps, my bad. I got user.dat and the win.ini confused. (Its been a long time.)shm wrote:Uhm, Actually, the windows registry isn't an .ini file.
You're mistakenly assuming that the purpose of GConf and the purpose of the Registry are the same.shm wrote:IMHO, GNOME abuses it's registry more than even Windows does

Bingo.lurid wrote:This is what Gnome attempts to avoid. ALL the options there, but they're not present within the application itself, thus minimizing confustion and bloat while maximizing productivity. Lets face it, business people generally aren't power users. They want to load their program and do what they need to do. There is no need to have millions of options all over the place. If you look at the people who use Gnome over KDE its this single point most of them point to; KDE has too many options and too cluttered of an interface. Gnome appears to be more simplistic by sticking all those options in a seperate program that no one but power users even know about, much less use regularly. But all the options are still there. It leads to a very nice elegant enviroment that doesn't overwhelm new users.
Yeah, but at the same time, I hate how GNOME uses gconf to hide configuration options in gconf, and then decides what's "advanced" and what's not. If the regular preferences dialogs were removed, I think there would be no problem. Mode-less GUI interfaces are always a good idea, and I think GNOME developers realized this in Nautilus but not gconf, unfortunatly. This is why I prefer KDE 3.x to GNOME 2.x, and I perferred GNOME 1.2 to GNOME 1.4 (that, and I liked gmc better than Nautilus)Toth wrote: Look through the Desktop Preferences menu in Gnome, then look at the KDE Control Center, and you'll be able to tell instantly why I use Gnome instead of KDE.
Well, I think the entire point is that most users won't touch any of the things that can be configured in gconf. But gconf allows power users to still go in and tweak them. I do see what you mean though...if gconf looked like a configuration dialog instead of the way it looks now it would be easier to adjust those settings. However, I don't mind the way it is now.shm wrote:Yeah, but at the same time, I hate how GNOME uses gconf to hide configuration options in gconf, and then decides what's "advanced" and what's not. If the regular preferences dialogs were removed, I think there would be no problem. Mode-less GUI interfaces are always a good idea, and I think GNOME developers realized this in Nautilus but not gconf, unfortunatly. This is why I prefer KDE 3.x to GNOME 2.x, and I perferred GNOME 1.2 to GNOME 1.4 (that, and I liked gmc better than Nautilus)Toth wrote: Look through the Desktop Preferences menu in Gnome, then look at the KDE Control Center, and you'll be able to tell instantly why I use Gnome instead of KDE.
If it were used just as a configuration system, like kconfig is in KDE, I'd have no objections.
I thought Gconf was more like an API: Anyone can write a new backend and a new frontend for it, so that you could, for example, make it an SQL database if you wanted.shm wrote:The latter..helmers wrote:: Is GCONF a database or a directory structure with real files in it?