Re: gconf relative to other GNOME config API's

[Ramiro Estrugo <ramiro eazel com>]

Colm Smyth wrote:
> 
> Hi,
> 
> GNOME already has two configuration API's which gconf is capable
> of replacing: gnome-config and gnome-mime-info. It is possible
> to re-write these API's in terms of GConf if required for
> backward compatability.
> 
> The gnome-mime-info keys include fm-open, fm-view, fm-ascii-open
> which are intended to specify file-management bindings. Nautilus
> appears to be using GConf directly.
> 
> Should we attempt to support/migrate package owners who have
> used gnome-config or gnome-mime-info?
> 
> Colm.
> 

Yes, Nautilus uses it directly.  There is at least one exception I can
think of.  For example, we use gnome_config to read the desktop
background settings.  These are written by the background caplet in the
control center.

Mike Engber wrote this code and if I recall, he mentioned something
about it being a pain that it was using gnome_config instead of gconf -
probably cause of the lack of callbacks in gnome config.

So yes, I think this is a good idea assuming you are willing to spend
the time to hack gnome_config to use gconf.  I cant imagine it being
more than a day or two of hacking.  

Of course you then need to test stuff to make sure nothing broke.  And
finally you need to make sure all the paths match.  Would all the path
strings continue to be the same ?  Would code that uses gnome_config
just work without any changes ?  

-re