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

[Neil Stevens]

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

On Monday February 03, 2003 08:55, Christoph Cullmann wrote:
> > >  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.

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.

- -- 
Neil Stevens - neil at qualityassistant.com
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+PqNSf7mnligQOmERAqE/AJ4gX64fFyCbPAbL+D/dswGnlpIN1ACdHX5W
10CxYHtbW7AiChYW/9LkMb4=
=TvDb
-----END PGP SIGNATURE-----