WM managed MDI (was Re: Three different tab implementations)

Christoph Cullmann cullmann at babylon2k.de
Mon Feb 3 16:55:51 GMT 2003

Hash: SHA1

> >  But a flexible universal MDI will require a lib, be it handled by the
> > lib itself or the WM. The lib may allow you to configure it so that
> > you'll get all tabs automatically undocked as toplevel windows even if
> > it implements the MDI all on its own. This one isn't a very good reason
> > why it should be the WM.
> Universal MDI require anything not in KMainWindow or KApplication.  If you
> require apps to go and add MDI-specific things, then it will not be
> universal.  Or else SDI-fan developers won't use it.
> And also, a universial *optional* MDI must be obeyed by an application
> developer.  If an MDI-fan developer does MDI in his app anyway, then a
> global SDI option won't have any efficacy.
A global SDI option is simply not doable at all, a app is mdi or not, the mdi 
style can be changed, for sure, but MDI stays MDI.

- -- 
Christoph Cullmann
KDE Developer, kde.org Co-Maintainer
http://www.babylon2k.de, cullmann at kde.org
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-core-devel mailing list