On 30/10/2012 04:11 PM, scott wrote:
>> From Orchid's postings, I gather that the Gsettings concept is
>> different in this respect, by having the applications just add or modify
>> their own private XML file, and then compile all such XML files into one
>> blob (for, as I suspect, faster access).
>
> This is quite a good idea, because then it's up to the OS to decide how
> to handle conflicts (eg if two apps try to set the same thing in their
> own XML). Also then when you uninstall you can just delete the XML and
> know that any settings from that app no longer have any influence. In
> Windows on the other hand it's simply whichever application changed the
> value most recently that wins.
>
> However does this mean that every time a program writes to the registry
> the OS must recompile everything?

Compiling just creates the key names and their default values. Actually 
reading and writing doesn't require recompilation.

Also, recompiling takes approx 400 ms on my virtual machine...

Let me just repeat again: Settings have default values. And textual 
descriptions [which are often less helpful than you'd like].

Under Windows, if you mistype the registry key, it just creates a new 
key [which then uselessly does nothing]. Under Gsettings, it whines "no 
such schema" or similar.

The *really* annoying part is that Gsettings appears to totally stop 
working if X isn't running. It's also maddeningly hard to change another 
user's settings...

Post a reply to this message