KConfigGroup (Re: KDE/kdelibs/khtml)

[Simon Hausmann]

On Sunday 11 February 2007 14:12:45 Stephan Kulow wrote:
> Am Sonntag, 11. Februar 2007 00:11 schrieb Aaron J. Seigo:
> > > I am strongly against this. People will write code like
> > > KConfigGroup group1("myconfigrc","group1");
> > > group1.writeEntry(..);
> > > KConfigGroup group2("myconfigrc","group2");
> > > group2.writeEntry(..);
> > > ... which will lead to myconfigrc being parsed twice. Very slow.
> >
> > sorry, my assumption was that we'd be using a KSharedConfigPtr internally
> > so this wouldn't be an issue.
>
> I think this falls into the category of "convenience trap" because you make
> it easier to define a global KConfig where a KSImpleConfig would be perfect
> - or you make it harder to define a read only config object than a normal
> one.

On the topic of KSimpleConfig: How about we merge KDesktopFile and 
KSimpleConfig is something like KConfigFile?

I at least find KSimpleConfig not a very descriptive name for what it 
represents and KDesktopFile seems to just add convenience on top.

Simon
-------------- 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/20070212/accc4335/attachment.sig>