[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: Removal of KAutoConfig / KAutoConfigDialog
From:       Benjamin Meyer <ben () meyerhome ! net>
Date:       2003-10-30 14:33:17
[Download RAW message or body]

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

On Thursday 30 October 2003 5:01 am, Waldo Bastian wrote:
> I would like to see KAutoConfig / KAutoConfigDialog / KCAutoConfigModule
> removed before KDE 3.2 gets released since more complete functionality is
> offered by KConfigDialogManager / KConfigDialog and kconfig_compiler.
> Having both set of classes unnecessarily fragmentates the KDE API.
>
> Note that there is no replacement for KCAutoConfigModule yet. At the moment
> it only seems to be used by kopete though.
>
> Most KAutoConfig usage has been converted to use KConfigDialog. Still to be
> done are:
>
> kdebase/kicker/applets/clock
> kdeaddons/kicker-applets/kbinaryclock
> kdenetwork/kopete
> kdemultimedia/kaudiocreator
>
> Cheers,
> Waldo

We are in string freeze and you want to modify kdelibs?  Anyone else see that 
as stupid?    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.  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.

- -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/oSEt1rZ3LTw38vIRAhTbAJwJ3UcQWQoU77WF5eKNAcpZh95e1QCcCBAH
3HGvgPcLtOcz0jTibMng+eU=
=wHZS
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]