The following sections discuss:
The following principles address choosing the parts of a window:
For more information, see the Information and Message Areas (Area) and Status Area (Area) reference pages.
Display secondary windows in the best possible location for the user. In some cases, this means that you need to let the user specify a default location for a particular secondary window, for example, a Find dialog window. The following principles address where to place a secondary window:
This keeps the windows from spreading unnecessarily over the entire screen. The user should be able to see the context from which the secondary window came and also to use the menu bar to access other secondary windows if needed.
In many cases, you need to position the secondary window so that it does not cover any part of the primary window. You can calculate the best location by beginning to the right of the primary window and moving the secondary window in a clockwise direction around the existing window until you find enough available screen space to display the secondary window. Do not cover up the title bar of the primary window. The user should be able to see the context from which the secondary window came.
The user should be able to see the context from which the secondary window came.
For more information, see the Secondary Window reference page.
Modeless secondary windows let the user continue to work in the existing window from which the secondary window was opened. Modeless secondary windows are more flexible than modal windows because users have greater control in the interface when they can interact with many windows.
Modal secondary windows prevent the user from continuing to work in the existing window from which the secondary window was opened. Use modal windows only when absolutely necessary, for example when a communications program is downloading a file that cannot be modified until the download has completed. Even though users cannot interact with elements within the existing window, they should still be able to interact with the existing window itself.
As an alternative to providing modal secondary windows, use a modeless secondary window and make some of the choices in the primary window unavailable.
For more information, see the Secondary Window reference page.
The following principles address conserving screen space:
A grid allows you to create visually appealing windows that accurately reflect the intended hierarchy. You can design a grid system to accommodate any size, shape, or quantity of information.
Grids promote consistency, allowing the user to anticipate placement of information from window to window.
Use group boxes judiciously. Although using group boxes effectively groups related controls together, group boxes provide visual clutter that can distract the user, especially when you use group boxes within other group boxes. Using separators and the design layout guidelines in this book can help minimize the use of group boxes.
Coherent typography presents a more cohesive, organized presentation of the information and makes it easier for the user to read. For example, use a bold font for headings and a light font for labels.
Line up similar elements and separate groups by placing a single colored line under the heading or by increasing the space between groups. Use indents to show sublevel information rather than nested group boxes. This saves screen space and keeps the windows organized.
In every composition there is positive and negative space. Positive space is the space taken up by elements such as icons and controls. Negative space is the space around the positive space. Software designers often think of this negative space as "extra" space. Although organizational techniques such as grid systems can help you compose a design that uses space economically, do not completely eliminate negative space because this space creates visual "breathing room" and enhances readability.