GConf is not tied directly to Gnome. It may be part of the Gnome
project, but it is usable without Gnome.
GConf currently requires GTK+ and ORBit. I agree that having these
additional libraries is a downside of using GConf. If we do an XML
configuration file then libxml2 is pretty much dependency free and it
will be more flexible, at the cost of more work for the implementation.
Tom
On Thu, 2004-03-11 at 11:12, David A. Desrosiers wrote:
> > I am not opposed to GConf, but I would like to hear some other opinions
> > (besides "GConf is like the registry") on which format we should use for
> > storing configuration going forward.
>
> My vote is for XML or text, definaately not GCConf, unless you want
> to tie it directly to GNOME. With the recent patch to remove GNOME support
> from Multisync ("text-only" mode), this becomes even more important.
>
> Any technology which ties itself intimately to one particular
> operating environment, is not going to extend itself easily into others.
>
>
> d.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Multisync-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/multisync-devel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel
