From kde-core-devel  Mon Dec 05 15:22:32 2005
From: Benjamin Meyer <ben () meyerhome ! net>
Date: Mon, 05 Dec 2005 15:22:32 +0000
To: kde-core-devel
Subject: Re: KDE/kdelibs/kdecore
Message-Id: <200512051219.45699.ben () meyerhome ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113379615210634
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart47247204.ufc3Eb4Xu4"

--nextPart47247204.ufc3Eb4Xu4
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 02 December 2005 11:46 am, Ian Reinhart Geiser wrote:
> 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.
>
> Cheers
>  -ian reinhart geiser

I would have to agree, Qt4's QSettings simplification to only having a valu=
e()=20
and setValue() make much more sense then attempting to add every possible=20
case.


=2DBenjamin Meyer

=2D-=20
aka icefox
Public Key: http://www.icefox.net/public_key.asc

--nextPart47247204.ufc3Eb4Xu4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDlHax1rZ3LTw38vIRAkpvAJ9MskckzOP2t8OZ592whEI1g1RLcgCdGEHI
btKND/MPyUmr35/XCt+6KP4=
=Q3xa
-----END PGP SIGNATURE-----

--nextPart47247204.ufc3Eb4Xu4--