configuration system notes
bastian at kde.org
Thu Apr 7 21:21:05 EEST 2005
On Thursday 07 April 2005 18:18, Avery Pennarun wrote:
> On Thu, Apr 07, 2005 at 12:01:20PM -0400, Havoc Pennington wrote:
> > On Thu, 2005-04-07 at 17:25 +0200, Buola Buola wrote:
> > > I think the loading/enforcing schemas should take place in the daemon,
> > > not in the client
> > GConf does this now, and it's wrong, and the web pages I posted explain
> > why.
> In fact, those web pages do a pretty lousy job of explaining why, but I
> actually agree with you. Three good reasons to enforce schemas at the
> frontend instead of in the daemon:
> - you can produce C/C++ headers from the schema, and actually load the
> configuration content directly into an optimized local data structure
> that will be faster and smaller while the app runs. (Of course this
> also gives you compile-time type checking in your app, which is nice.)
FWIW, This is the approach that KConfigXT follows. Not only does it do
compile-time type checking it also does compile-time typo ¹ checking :-) I
think the latter is actually more important than the former.
¹ typo as in: saving a setting to "Color" and reading it back from "Colour"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/xdg/attachments/20050407/49fd1e5f/attachment.pgp
More information about the xdg