RFC: Removal of KAutoConfig / KAutoConfigDialog

[Cornelius Schumacher]

On Thursday 30 October 2003 15:33, Benjamin Meyer wrote:
>
> We are in string freeze and you want to modify kdelibs?  Anyone else see
> that as stupid?

I don't see how the string freeze is related to removing the KAutoConfig 
classes. This won't change any strings, will it? That there are multiple 
classes which do almost the same thing is a bug in the API which has to be 
fixed.

>    There are a number of classes in KDE that are marked as
> volital do the same.  I would have to say that kconfig_compiler
> uncesessarily fragmented the KDE API _in a freeze_ not the other way
> around.

Moving KConfigSkeleton and kconfig_compiler to kdelibs removed  quite some 
duplication and fragmentation in the modules. It didn't viloate the freeze as 
it was in the feature plan and was done before the final freeze.

>  As even you yourself point out there are still apps that use it
> and the
> KCAutoConfigModule functionality can't be replaced.  The KDE clock is a
> pretty prominent application and I think there are many who will agree with
> me.  Mark the classes as volital and move on.

The classes have never been part of a KDE release, so now is the right time to 
remove them. Putting classes into a release which are obsolete even before 
the release doesn't make much sense.

-- 
Cornelius Schumacher <schumacher at kde.org>