KDialogBase

[Falk Brettschneider]

Hi,

Ralf Nolden wrote:
> 
> Richard Dale wrote:
> >
> > I don't like MDI, and won't use an IDE which forces that UI paradigm
> > onto me (I am not a Microsoft refugee)
There's always confusion about the word "MDI". MDI in the strict
historical sense means Microsoft's Childframe mode (mainframe covering
floatable child views). I think that is what you mean.

If a good programmer talk about MDI, he only means a program
architecture which can handle many documents and views. When talking
about MDI the GUI is not of interest, actually. Gimp is an MDI
application as well KDEStudio. You always deal with _many_ documents
(files) there. The class DocViewMan is actually the only thing in
KDevelop that defines it to be a good MDI application.

The visualization of your Multiple-documents-multiple-views architecture
is of secondary interest. It doesn't matter to the whole program and one
can put it in a separate code part. That is done with the QextMDI
library which simply provides you with several modes for VISUALIZING
MANY VIEWS, not depending on your application architecture.

At the moment we have 3 such visualization modes: Gimp-like,
KDEStudio-like and common Microsoft-like.
One can imagine also a 4. mode: Kate/Kant-like.

> But since the window menu is all tied into QextMDI this is kind of
> not changable, or Falk ?
That's not true.
QextMDI suggests you to use QextMdiMainFrm::windowMenu() that you can
insert in your main menu but you can ignore it and use your own
windowMenu() or you can override it in your inherited mainwidget class
since QextMdiMainFrm::windowMenu() is virtual public or protected.

> have to agree KDE-wide for a standard on MDI because this *is* confusing
> the user.
IMO not a user who is a developer.

> Ralf
F at lk


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«