AW: [RFC] KConfig merge

[Nhuh Put]

> Von: Andreas Pakulat
> Gesendet: Dienstag, 2. Oktober 2007 21:41
> An: kde-core-devel at kde.org
> Betreff: Re: [RFC] KConfig merge
> 
> On 02.10.07 21:01:03, Nhuh Put wrote:
> > Ok, later then expected, but I'm ready.
> > /branches/work/kde4_kconfig/kconfig (the rest of kde4_kconfig is
> outdated)
> > It's basically a large refactoring of KConfig.
> > There are still some overloads for some methods missing, but this half
> an
> > hour of work.
> > Unfortunately I can't really test it and I also don't have the compile
> power
> > to port very much myself. In most parts it's only KConfigBase->KConfig.
> > It would be really nice to have this, because it's not possible in a BC,
> but
> > nobody will die, if this isn't in KDE 4.
> > So the question if, weather I can import it into trunk. If yes, some
> helping
> > hands with lots of compile power would be nice.
> 
> I have amarok, koffice, kdebase, kdenetwork, kdegraphics, kdegames,
> kdevelop stuff, kdesdk, plasma from playground and kdemultimedia here.
> The problem is: I'm going to be away for the next 3-4 hours. I'll be
> here after that so if you need help then I am willing to do that as long
> as its really mostly a s/KConfigBase/KConfig/
> 
> Andreas
> 
> --
> You like to form new friendships and make new acquaintances.

Hello
We tried very hard, but we couldn't get this ready for today.
The main problem is, that the header structure of the config classes is now
much clearer, which (they now only the things in the really nead, which is
much less hen before) leads to many compile errors all over the place.
There are also some small changes to KConfigGroup and the removal of
KConfigFlags. These problems are mostly very easy to fix, but as those
classes are used nearly everywhere it's still a huge amount of work. We
would do the porting a work in a branch and merge it back into trunk later.
We would probably need one or two days to fix everything.
I know, it's past the freeze date (or will be before we are ready), but this
would be a huge improvement over the current situation. As I already said,
the header structure is much clearer (kconfiggroup.h does currently include
kdebug.h for example) and the API is much clearer and easier to understand.
The Backend classes are largely separated from KConfig (no friend
declaration for every backend anymore) and the internal structure has much
improved. Also the API is prepared to handle different non-file config
backends and nested groups (which are partially implemented). Also the
arguments types for the read and write methods are now more consistent.

For those reasons, I would like to ask for an exception form the API freeze
for this patch, especially as this can't be done later in a BIC way.

The changes are in branches/work/kde4_kconfig/kconfig together with a patch
for kdelibs.

	PutHuhn