Moving QExtMDI to kdelibs

Jason Keirstead jason at
Tue May 13 23:05:06 BST 2003

On May 13, 2003 06:44 pm, Neil Stevens wrote:
> On Tuesday May 13, 2003 02:39, Jason Keirstead wrote:
> > I think this QExtMdi would be excellent in kdelibs because finally all
> > these MDI apps can have a consistant interface and features. Right now
> > they all behave differently. But the ability to switch from tab mode to
> > to level mode on the fly in apps like Konq and Kate and KOffice would be
> > a dream come true for me.
> If that's how you feel, then please propose your own guideline for when to
> forbid MDI, when to allow MDI, and how to implement MDI.
> Should MDI be on by default?  Should a KDE MDI default be centralized?
> Does this MDI library even support this kind of consistency we expect in
> KDE?

I think I just answered most all these questions in the above paragraph.

When to forbid - Never for apps with a document driven interface. Forget MDI / SDI,
why should we be able to *forbid* the user from doing anything?

Should it be on by default - Depends on what you mean by "on". I think
by default, File->New should probably always open a new window, as should
File->Open. but if the particular app has a document based method for opening
a new MDI window, like Konq's middle click, that is intuitive and does not interfere
with  existing keybindings, I see no problem with that. Also of course you should be
able to switch to one of the MDI modes (windows, tabs, whatever) so these actions
all use MDI.

Should MDI in KDE be centralized - yes. 

Should a default setting determine MDI for all apps - Maybe for initial app defaults, but
surely all apps should store their own settings as well. Just because I want tabs in Konq
does not mean I want them in KWord.

As for the library, I have no idea I never even looked at it. I am just relaying my opinions
with regards to MDI usage in general.

Jason Keirstead, BCS

More information about the kde-core-devel mailing list