Ian Reinhart Geiser geiseri at yahoo.com
Fri Dec 2 16:46:16 GMT 2005

On Friday 02 December 2005 09:29 am, Oswald Buddenhagen wrote:
> On Fri, Dec 02, 2005 at 01:20:22PM +0000, David Faure wrote:
> > SVN commit 484988 by dfaure:
> >
> > Ingo's wish is my command: adding writeEntry(key,QList<QByteArray>)
> > and readByteArrayListEntry.
> i think inflating the KConfigBase api with increasingly specialized and
> weird read*Entry and writeEntry methods goes into the wrong direction.
> the imo right approach is having to/fromString methods in the classes
> themselves. the remaining classes can have marshallers in KConfigBase
> or (preferably?) some other class - that would particularly apply to
> QList<>.
> in any case it is essential to have the un-/marshallers available
> separately, so one can nest them freely. i missed such a possibility
> repeatedly.
> the {read,write}Entry core should be template-based, with explicit
> instanciations for the common cases (PODs, string lists and various
> other Q types - well, the sane part of the current api).
Really I think the QSettings direction is way more useful to me as a 
developer.  With the current KConfig api I have to remember a million 
methods, and if they even exist.  With the QSettings api, i just have to 
remember that the value is a valid QVariant.  

Just my 2c though.

 -ian reinhart geiser
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051202/351dec1d/attachment.sig>

More information about the kde-core-devel mailing list