RFC: Removal of KAutoConfig / KAutoConfigDialog

[Tobias Koenig]

On Wed, Nov 12, 2003 at 09:24:24PM -0500, Benjamin Meyer wrote:
Hi,

> > > 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.  
<nitpicker>
So why don't you save these thirty eight additionally seconds by painting it
the right color immediately?
</nitpicker>

If KAutoConfig is so similar to KConfig_Compiler why porting it first to
KAutoConfig and then with a quick hack to KConfig_Compiler... that makes
no sense IMHO.

Ciao,
Tobias
-- 
Can a government that shoots at reporters be democratic?
Separate politics from religion and economy!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031113/1bdb5aa1/attachment.sig>