About Face 2.0(c) The Essentials of Interaction Design
If dialog boxes were independent programs, they would be transient-posture programs. As you might expect, dialog boxes should then look and behave like transient programs, with bold, visual idioms, bright colors, and large buttons. On the other hand, dialogs borrow their pixels from sovereign applications, so they must never be wasteful of pixels. The imperative to be large is constantly at war with the imperative to be small. One solution is to make each of the individual controls slightly larger, but to make sure that the dialog itself wastes no additional space.
DESIGN TIP | Dialogs should be as small as possible, but no smaller. |
Borland popularized a standard by creating extra-large butcons with bitmapped symbols on their faces: a large red X for Cancel, a large green checkmark for OK, and a big blue question mark for Help. They were cleverly designed and very attractive—at first. Most people, with good reason, now find them wasteful of space. The icons on the butcons worked well to visually identify themselves, well enough that the extra size wasn't necessary. Borland now uses the same bitmaps on buttons of a more conventional size, which is a much better solution. The visual images accomplish the job just fine without the need to waste precious pixels.
Obscuring the parent window with dialogs should be minimized. Dialog boxes should never take more room than they need. Pixels remain the most limited resource in modern desktop computers, and dialog boxes shouldn't sprawl across the screen. Compare the space efficiency of the CompuServe Navigator dialog in Figure 31-1 to the one from Word in Figure 31-2.
Check boxes are a relatively space-inefficient control: the accompanying text requires a lot of dedicated space. Compared to the text of check boxes, butcons can be crammed together like sardines. But even check boxes don't need the kind of room they were given in the Navigator dialog.
|
|