[Kst] .ui.h file removal

[Barth Netterfield]

Being infinitely conservative, I prefer the inheritance approach over the 
designer approach.  It is more flexable, and one gets to program in one's 
editor of choice, and you always know where to find the code you are looking 
for (its not hiding somewhere).

I know of no big advantages to using designer however... (other than perhaps 
slightly less complicated code - no inheritance.

cbn

On March 29, 2004 05:20 pm, Andrew Walker wrote:
> There was no particular reason for the removal of the .ui.h
> file othar than that I prefer not to have Qt Designer handle
> too much of anything. It always seems to me that you can
> go so far with it and then it starts to fall apart. Inheritance
> is more painful to start with but can be less so in the
> long run. But it comes down to personal preference.
>
> Andrew
>
> > Date: Fri, 26 Mar 2004 11:31:14 -0500
> > From: George Staikos <staikos at kde.org>
> > Subject: Re: [Kst] kdeextragear-2/kst/kst
> > To: kst at kde.org
> > Message-ID: <200403261131.14388.staikos at kde.org>
> > Content-Type: text/plain;  charset="utf-8"
> >
> > On Friday 26 March 2004 11:06, Andrew Walker wrote:
> > > CVS commit by arwalker:
> > >
> > > Added for log table...
> > >
> > >
> > >   A            kstlogtable.cpp   1.1 [GPL (v2+)]
> > >   A            kstlogtable.h   1.1 [GPL (v2+)]
> >
> >   Thanks.  What was your reasoning for removing usage of the .ui.h file
>
> for
>
> > debugdialog?  I don't think inheritence gains anything over the .ui.h
> > file
>
> in
>
> > this case.  The reason the other dialogs don't tend to use .ui.h is
>
> because
>
> > designer didn't support that at the time they were made.  I think we
>
> should
>
> > use .ui.h files for new dialogs though.
> >
> > --
> > George Staikos
> > KDE Developer				http://www.kde.org/
> > Staikos Computing Services Inc.		http://www.staikos.net/
>
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst