Content deleted Content added
→See also: link center stage |
Link suggestions feature: 2 links added. |
||
| (One intermediate revision by one other user not shown) | |||
Line 12:
===Advantages===
* With multiple-document interfaces (and also [[tabbed document interface]]s), a single [[menu bar]] and/or [[toolbar]] is shared between all child windows, reducing clutter and increasing efficient use of screen space. This argument is less relevant on an operating system which uses a common menu bar.
* An application's child windows can be hidden/shown/minimized/maximized as a whole.
* Features such as "Tile" and "Cascade" can be implemented for the child windows.
* Authors of [[Cross-platform software|cross-platform]] applications can provide their users with consistent application behaviour between platforms.
* If the windowing environment and OS lack good window management, the application author can implement it themselves.
* Modularity: An advanced window manager can be upgraded independently of the applications.
Line 41:
* [[Kate (text editor)|Kate]]: Text editor designed for the [[KDE Software Compilation]], with advanced features and a sophisticated MDI
* [[Macromedia Studio]] for Windows: a hybrid interface; TDI unless document windows are un-maximized. (They are maximized by default.)
* [[Microsoft Excel]] 2003: SDI if you start new instances of the application, but MDI if you click the "File
* [[Microsoft Word]] 2003: MDI until [[Microsoft Office]] 97. After 2000, Word has a [[Multiple Top-Level Windows Interface]], thus exposing to shell individual SDI instances, while the operating system recognizes it as a single instance of an MDI application. In Word 2000, this was the only interface available, but 2002 and later offer MDI as an option. [[Microsoft Foundation Classes]] (which Office is loosely based on) supports this metaphor since version 7.0, as a new feature in [[Visual Studio]] 2002. SDI only as of 2013.
* [[Mozilla Firefox|Firefox]]: TDI by default, can be SDI
| |||