RFC: Removal of KAutoConfig / KAutoConfigDialog

[Benjamin Meyer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Aat the same 
> time there was a decision made to use a different set of classes, and i
> think some of us are concerned that your efforts are not being put to full
> use as they are going into further adoption of the deprecated set of
> classes.

Well have a whole bunch of work that was done before the decision was made so 
it isn't like I am continuing to port stuff to KAutoConfig, just trying to 
figure out what to do with all the code I have.

> outside of the cold world of technical reasons, here's how i feel (yeah, a
> four letter word;) about this: i'm sure that having your classes put into
> kdelibs was exciting, and having them pulled out again just as
> dissapointing.

Yes it was disappointing, but it wasn't that big of a deal.   KConfigXT is 
better, is more flexible, and does include code from kautoconfig.  But I was 
pissed about the way that it forced on cvs.  There was no announcement on the 
lists, just a massive dump on cvs that was so big and touched so many thing 
that it couldn't be reverted.  But I stated this all when it happend and no 
one cared, so I just let it be

http://lists.kde.org/?l=kde-core-devel&m=106507219611784&w=2

At the time that it happend it didn't really matter if the solution was 
technically better or not, a good chunk of code I had touched in the last six 
months was modified and that code had obviously been put there by me.  
Wouldn't it tick you off just a little bit if that was done to you without 
even an e-mail of heads up?  In some companies if you even correct comments 
in code that isn't yours, you can be fired.  That is of course not how KDE 
works.  I have become used to the idea that others would modify my code and 
even look forward to seeing what others find/catch/improve that I missed.  
But at the same time those modifications have always been on the smaller side 
and anything that really impacted code I am working on an e-mail with the 
idea and maybe even a patch was brought up so that we could discuss it.  This 
is what rule number eight of the KDE CVS Commit Policy is all about.

Anyway... I have a bunch of apps that I have ported to KAutoConfig (with the 
authors permission first).  I'll spent some time and port them all to 
KConfig_XT and commit them once the tree opens up again.

The KAutoConfig class should be copied to:
kdemultimedia/kaudiocreator/
kdebase/kicker/applets/clock
kdeaddons/kicker-applets/kbinaryclock

Am I missing anywhere?

Then removal of KAutoConfig and the KAutoConfig tutorial

The KAutoConfigDialog needs to be rename it to KConfigDialogManager and rip 
out the KAutoConfig parts (which will no longer be in kdelibs).

Shale I do this or do someone else want to?

- -Benjamin Meyer

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/swjL1rZ3LTw38vIRAhI5AKC0Wxy8BHLF9c1qA0AXgFh7R/poAACfbEtL
j01Bc3JhBQ5r5pJ6NnpBWpo=
=5ddD
-----END PGP SIGNATURE-----