KAutoConfigDialog

[Benjamin Meyer]

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

On Wednesday 16 April 2003 4:18 am, Waldo Bastian wrote:
> On Tuesday 15 April 2003 22:17, Benjamin Meyer wrote:
> > I have attached the classes for others to look at.  They arn't all that
> > much. They arn't suppost to replace all of the functionality of
> > KDialogBase, but just enough so the average application can bring up it
> > settings dialog.  I have this class in use in more then two applications
> > and it is usefull in most applications.  Are there any major objections
> > to moving it into kdeui?
>
> I don't think it is very scalable since it insists on doing the layout
> stuff itself.

I agree that it doesn't allow for much scallability for that reason, but in 
the majority of cases I think the class would sufice and I am open to any 
option for improving it to scale better.

>When the number of options in your dialog increase there
> comes a time that you want to actually order them, that will not happen if
> it means that you have to redesign much of the code in order to move from
> KAutoConfigDialog to some .ui file driven approach.
> The right approach IMHO is to use .ui files from the begin. That way the UI
> can be designed driven by UI concerns and not driven by limitations of the
> implementation.

I am not sure I follow you on this.  The order of the dialog is determined by 
the order of the widgets that are put in.  Also in the example I gave (KTron) 
the three objects pass were just three ui generated files will no actual 
developer written code.  Could you explain a little more?

- -Benjamin Meyer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+nRSx1rZ3LTw38vIRAhLWAJ9cfuLuMafqNmFeltnbEmyZOomFPgCaA9uH
5QHackDROPB/o5TN+h2aGwg=
=mjQ7
-----END PGP SIGNATURE-----