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

Christoph Cullmann cullmann at babylon2k.de
Mon Feb 3 17:32:35 GMT 2003

Hash: SHA1

> > > 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.
> Well, it's not doable if certain MDI developers refuse to accomodate SDI
> users, that's true.  But I think within KDE we assume that all apps are
> required to obey the standards, and we can write kdelibs such that
> non-standard apps require special effort to achieve.
Now you again call MDI apps non-standard ? Wasn't there now the agreement that 
MDI is "good" and usable in some areas ? Wasn't the whole disscussion here 
about how to strip the different mdi codebases away to have one default way 
of handling mdi in kdelibs instead of the different apps to increase the 
usability and GUI of that apps (as there would be one unique style for 
handling mdi then) ?


- -- 
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