[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] KCoreConfigSkeleton
From:       Oswald Buddenhagen <ossi () kde ! org>
Date:       2007-11-25 19:01:28
Message-ID: 20071125190128.GA18836 () ugly ! local
[Download RAW message or body]

On Sun, Nov 25, 2007 at 07:31:24PM +0100, Cornelius Schumacher wrote:
> On Sunday 25 November 2007 18:41:14 Oswald Buddenhagen wrote:
> > - the typing system looks unnecessarily complex. i would think
> > everything could be done via variants (after registering some custom
> > types for passwords, paths, etc.). the type of the entry would be
> > defined through the default, just like in kconfiggroup. all the
> > conversion stuff is in kconfig already (or should be, fwiw).
> 
> The complexity in the implementation gives better type safety for the
> user than a QVariant based API. So I wouldn't call this unnecessary.
> 
have you looked at the kconfiggroup implementation lately? it deals with
qvariants internally (and offers this as api), but there is also a
type-safe template based api on top of it. i'd do the same for the
skeleton.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
[prev in list] [next in list] [prev in thread] [next in thread]