Moving QExtMDI to kdelibs

[Christoph Cullmann]

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

> So what we should do now in my opinion is doing the second step before
> doing the third one. First let Lubos implement a Kwin based MDI, using
> QExtMDI if it helps, not using it if it doesn't. After that everyone can
> work on communication between SDI applications through the MDI framework
> offered by Kwin. After that the whole SDI vs. MDI discussion in only up to
> the user's personal experience and preference.
qextmdi allready supports some toplevel mode for all views, which look much 
like the "controlled sdi mode" out of our current styleguide. the whole 
window manager stuff can be nicely hidden into qextmdi backend later if done, 
or ? And to enforce SDI as default mode for kdevelop/quanta/kate/... is not 
realistic (looking at how the apps work and what they want to archive and 
last but not least usability wise, 100 opened editor windows while working in 
kdevelop won't be that nice per default, or ?) and not wanted by the devs of 
that apps, or I am wrong here ?

cu
Christoph

- -- 
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann at kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+xSjVyPjDGePm9UIRAi0eAJ9BpsSuTRuVsbLM3/kRdmVfZcLyxQCfQEae
BdKzVvib2dtDU3V4AfXbCL8=
=Tucc
-----END PGP SIGNATURE-----