Re: GConf vs. bonobo-config



Martin Baulig wrote:
> 
> Nobody says that you must use it, just stick with GConf.
> 
> Nautilus is a large end-user application, and as GNOME 1.4 application I guess
> it uses only GConf for all its configuration.
> 
> You only "need" to port it to bonobo-config if you want to read/write configuration
> data which is shared between Nautilus and other applications.

Hrm...I maybe on crack but....

	Where do non-component [non-bonobo] based apps fit into this?

If we start using bonobo-config, which *isn't* a wrapper for gconf [which I assume
from the discussion], for component based apps and GConf for non-component based
apps [which we have no alternative - except using CORBA when we don't really need] 
then we have a big, ugly mess...

I agree that it would be good to have a component/CORBA wrapper around GConf but 
I'm not sure if introducing a seperate configuration mechanism is good for GNOME?



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]