Multiple document interface
From Wikipedia, the free encyclopedia
Graphical computer applications with a Multiple Document Interface (MDI) are those whose windows reside under a single parent window (usually with the exception of modal windows), as opposed to all windows being separate from each other (single document interface). The initialism MDI is usually not expanded. In the usability community, there has been much debate over which interface type is preferable. Generally SDI is seen as more useful in cases where users work with more than one application. Companies have used both interfaces with mixed responses. For example, Microsoft has changed its Office applications from SDI to MDI mode and then back to SDI, although the degree of implementation varies from one component to another.
The disadvantage of MDI usually cited is the lack of information about the currently opened windows: In order to view a list of windows open in MDI applications, the user typically has to select a specific menu ("window list" or something similar), if this option is available at all. With an SDI application, the window manager's task bar or task manager displays the currently opened windows. In recent years, applications have increasingly added "task-bars" and "tabs" to show the currently opened windows in an MDI application, which has made this criticism somewhat obsolete. Some people use a different name for this interface, "tabbed document interface" (TDI). When tabs are used to manage windows, individual ones can usually not be resized.
Nearly all graphical user interface toolkits to date provide at least one solution for designing MDIs. GTK+ lacks any standardized support for MDI. The Java GUI toolkit, Swing, for instance, provides the class javax.swing.JDesktopPane which serves as a container for individual frames (class javax.swing.JInternalFrame).
Contents |
[edit] Compared to single document interface
[edit] Advantages
- Many child windows do not fill up the OS task management interface, as they are hierarchically organized. Users simply switch applications.
- With MDI (and also TDI), a single menu bar and/or toolbar is shared between all child windows, reducing clutter and increasing efficient use of screen space.
- All child windows for an application can be hidden/shown/minimized/maximized as a whole.
- Without an MDI frame window, floating toolbars from one application can clutter the workspace of other applications, potentially confusing users with the jumble of interfaces.
- Features such as "Tile" and "Cascade" can be implemented for the child windows.
[edit] Disadvantages
- Cannot be used successfully on desktops using multiple monitors.
- Cannot be used successfully with multiple virtual desktops.
- MDI can make it more difficult to work with several applications at once, by restricting the ways in which windows from multiple applications can be arranged together.
- The shared menu changes, which may cause confusion to some users.
- MDI child windows behave differently from those in single document interface applications, requiring users to learn two subtly different windowing concepts. Similarly, the MDI parent window behaves like the desktop in many respects, but has enough differences to confuse some users.
- Many window managers have built-in support for manipulating groups of separate windows, which is typically more flexible than MDI in that windows can be grouped and ungrouped arbitrarily. A typical policy is to group automatically windows that belong to the same application. This arguably makes MDI redundant by providing a solution to the same problem.
[edit] Application Examples
- Internet Explorer 6: This is a typical SDI application
- Visual Studio 6 development environment: This is a typical modern implementation of MDI
- Visual Studio .NET: MDI or TDI with "Window" menu, but not both
- Firefox: TDI by default, can be SDI instead
- Opera: MDI combined with TDI
- GIMP: Floating windows (limited MDI is available via "Deweirdifier" plugin)
- GIMPshop: A fork of the GIMP edited to be more user-friendly for Adobe Photoshop users. Note: the Windows version (still in beta form) has the "Deweirdifier" plug in built-in
- Adobe Photoshop: Floating windows in Mac version; MDI in Windows XP version. In newer versions of Photoshop, toolbars can move outside the frame window. Child windows can be outside of the frame unless they are minimized or maximized.
- Adobe Acrobat: Purely MDI until version 7.0. (Microsoft Windows version only)
- Microsoft Excel 2003: Excel is SDI if you start new instances of the application, but classic MDI if you click the "File → New" menu (except the child windows appear on the OS taskbar)
- Microsoft Word 2003: Up to Office 97, Word was MDI. However, from 2000 onwards, Word is a Multiple Top-Level Windows Interface application, thus exposing to shell as many individual SDI instances while the operating system recognizes it as a single instance of an MDI Application. MFC (which Microsoft Office is loosely based upon) supports this metaphor from version 7.0, as a new Feature in Visual Studio 2002.
- UltraEdit: Combination of MDI & TDI (a true MDI interface with a tab bar for quick access).
- Notepad++: TDI
- Macromedia Studio under Windows uses a hybrid interface. If document windows are maximized, as they are by default, the program presents a TDI, however, if the windows are un-maximized it presents an MDI.
- Corel Wordperfect: MDI, although a user can open multiple instances of WP with a single document in each, if they wish to. Version X3 maintains a list of open docs for a given window on the status bar at the bottom of the window, providing a variant of the TDI. (earlier version info needed)
[edit] Classic examples
This is a list of examples from back in the days of Windows 95, and Windows 3.x
[edit] See also
[edit] External links
- Interface Hall of Shame arguments against MDI
- Mailing list debate about GTK+ / GIMP support for MDI
