post 3.3 kconfig_xt work

[Benjamin Meyer]

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

On Thursday 12 August 2004 4:08 pm, Frans Englich wrote:
> On Thursday 12 August 2004 15:53, Maks Orlovich wrote:
> > On Thursday 12 August 2004 10:41 am, Benjamin Meyer wrote:
> > > On Wednesday 11 August 2004 10:20 pm, Maks Orlovich wrote:
> > > > On Wednesday 11 August 2004 08:08 pm, Benjamin Meyer wrote:
>
> <snip>
>
> > Do you have any numbers to back this up, in particular on the first 2
> > points? If you don't, you're just making stuff up.
>
> Can't you convince yourself by you doing the research? I consider it pretty
> hard finding people who don't want their applications to use KConfigXT.
>
> 			Frans

Before it was KConfigXT and was KAutoConfig the first app that was ported 
KTron was reduced by about half in all departments.  This was one of the 
really exciting parts about converting apps to KAutoConfig.  Now that will 
hardly apply for more typical larger apps and not as much so with the 
KConfigXT class.  Just about every port involves ripping out several (if not 
numerous) custom classes/functions that were written for that application.  
If I can dig up the exact numbers for ktron i'll post it up later tonight

- -Benjamin Meyer

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

iD8DBQFBG/xL1rZ3LTw38vIRAj3UAKCVU+v9eUoAdlsagH1PuPD5SUu5agCfdNTi
U+TDf2TLEr7adu8CR3p7ee8=
=ewVL
-----END PGP SIGNATURE-----