Moving QExtMDI to kdelibs

Neil Stevens neil at
Tue May 13 23:05:19 BST 2003

Hash: SHA1

On Tuesday May 13, 2003 03:02, Christoph Cullmann wrote:
> > > If this library were in kdelibs, you wouldnt *have* to make that
> > > decision, because it has a toplevel mode. In fact, IMO, the ideal
> > > situation would be for every single KDE document based app to use
> > > this library, with toplevel mode as the default. Then the *user*
> > > decides when to use MDI and when to not use it, which is what should
> > > always be the situation, IMO. Developers should not dictate to users
> > > how they should use their machines.
> >
> > Even if QExtMDI would be in kdelibs, I don't think it would be a good
> > idea to make general use of it, because it introduces complexity and a
> > potential source for bugs. In my opinion developers should concentrate
> > on debugging the functionality of an app not the way it arranges its
> > views.
> Which is for many apps who work with many documents at once a top point
> of the functionality, kdevelop would be useless if it splatters the
> editorwidgets around the screen.

Here we go again.  IF that's true, then it should be fixed in the window 
manager, instead of making every app its own window manager.

It sounds to me like you only ever need to do one thing at a time, so you 
don't have a problem of needing different documents on different desktops 
for different tasks.  If you did, then you'd see how this MDI limitation 
is so bad.

- -- 
Neil Stevens - neil at
"The shepherd drives the wolf from the sheep's throat, for which the
sheep thanks the shepherd as a liberator, while the wolf denounces him
for the same act as the destroyer of liberty." -- Abraham Lincoln
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-core-devel mailing list