RFC: Removal of KAutoConfig / KAutoConfigDialog

Waldo Bastian bastian at kde.org
Thu Nov 13 09:15:27 GMT 2003


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

On Thu November 13 2003 01:12, Benjamin Meyer wrote:
> Did you even bother reading my post?  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.

It will be less work to port directly to KConfig_Compiler + KConfigDialog than 
via KAutoConfig. For example, the default values don't need to be added to 
the .ui files. Also, KAutoConfig has some restrictions that KConfig_Compiler 
doesn't have that may make porting via KAutoConfig unnecassery difficult.

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SUSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/s0uvN4pvrENfboIRAhouAJ4maC51FiOssv+2Dkj+2rBlScI/TgCfQHgZ
Tyvl3ivLMnQ9uX2oI1zbuEg=
=MfRd
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list