RFC: Removal of KAutoConfig / KAutoConfigDialog

[Benjamin Meyer]

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

> > When an application is ported to use
> > an auto configured dialog be it KAutoConfig or KConfig_Compiler you have
> > to do the __SAME__ thing!  It is like building two cars, but one is blue
> > and one is red.  Just because the color is different doesn't mean that
> > 99% of the work isn't the same.
>
> Right, but your blue car is being painted red first, then being painted
> blue afterwards.

Yah, but when it takes 4 days to build a car and thirty eight seconds to paint 
the car suddenly that little detail of building the car makes a big ass deal.  
Port any generic app that doesn't use KAutoConfig to KConfigXT and then port 
an app from KAutoConfig to KConfigXT and then come back and tell us how I was 
so wrong and I all the work I did was a wasting of time.  I am sure waba 
could testify just how easy it was to port from KAutoConfig vs not having 
that common code infrastructure in place.

> In essence: you might as well port to KConfigXT, not add
> dependencies to depracated classes.

No.  I will simply not commit all the work I have done once head opens again.  
I'll let you and everyone port them yourselves sense what I have done is 
"just a waste of time" and you wouldn't want it anyway.

And your welcome for all of the work I have done so far.

- -Benjamin Meyer

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

iD8DBQE/sutb1rZ3LTw38vIRAqXzAJ9Uc5KboAkmXLrnXtUrKZuM5fB8/gCeNpZL
aLqoWifHVnjbG3pVjTpGZ30=
=sM2a
-----END PGP SIGNATURE-----