RFC: Removal of KAutoConfig / KAutoConfigDialog

[Benjamin Meyer]

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

On Thursday 13 November 2003 5:14 am, Rob Kaper wrote:
> On Thu, Nov 13, 2003 at 10:30:01AM +0100, Waldo Bastian wrote:
> > > The KAutoConfig class should be copied to:
> > > kdemultimedia/kaudiocreator/
> > > kdebase/kicker/applets/clock
> > > kdeaddons/kicker-applets/kbinaryclock
> >
> > The two clock applets have been converted to KConfigDialog already. The
> > only one left on my list is kdemultimedia/kaudiocreator. Will have a look
> > into that one today.
>
> Um, freeze?
>
> Not all applications have been ported to KConfigDialog before the freeze
> started, so you *can't* remove KAutoConfig from the API, which has the
> benefit that applications like Kopete won't need to carry a copy with
> it.
>
> Pick one please:
>
> a) KAutoConfig is so broken that these ports are necessary and justified,
> in which case we should not release KDE with Kopete using that broken
> KAutoConfig.

Where did this come from?  KAutoConfig isn't broke at all, it is simply being 
replaced with something that does more.

> b) We don't mind Kopete using KAutoConfig because it's not broken, in which
>    case porting to KConfigDialog cannot be justified because of the feature
>    freeze.
>
> Rob

This was already discussed in a previous thread.  Porting anything in cvs 
to/from KAutoConfig/KConfig_XT shouldn't happen in cvs currently as it is 
frozen.  KOpete already has a copy of KAutoConfig in its compact folder.

- -Benjamin Meyer

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/s5QS1rZ3LTw38vIRAi5tAJ9FWA64AosV5VPi8e+g/CSSp/EvkwCgj01W
M1nxSE7BRXCXq1tVAKsESs0=
=Hzwy
-----END PGP SIGNATURE-----