Choosing Appropriate Interface Features

Given the differences between how applications and utilities are used, it should be clear that not all user interface features work equally well in both program types. The user interface features suitable for each program type are discussed below.

Applications

The following list describes user interface strategies and characteristics appropriate for an application:

  • An application can use either a multiple-document interface (MDI) or a single-document interface (SDI).
  • For an SDI application that manipulates actual documents, the program must support running multiple instances in order to handle multiple documents simultaneously.

TIP
SDI programs that manipulate actual documents must support running multiple instances.

  • An application's main window should be maximized by default. For MDI applications, the MDI child document windows should most likely be maximized by default as well. Of course, the application should allow users to override these defaults.
  • Since applications are used for an extended period of time, an application's appearance should not be distracting or fatiguing. Consequently, its overall appearance should be low-key and its colors subdued.
  • An application should include an optional, configurable toolbar to support advanced users.
  • An application should support advanced user interfaces—such as keyboard shortcuts, context menus, and direct manipulation—to support advanced users.

Utilities

The following characteristics and strategies are appropriate for utilities:

  • A utility can use either an SDI or a dialog box interface. Using an MDI is definitely not recommended, since it requires too much effort to manage all the windows.
  • For an SDI utility that manipulates actual documents, the program must support running multiple instances in order to handle multiple documents simultaneously.
  • A utility's main window should have a flexible layout so that it can be used in a variety of sizes. The utility's main window should never be maximized by default.
  • Since utilities are not used for an extended period of time, a utility can use more and brighter colors than an application does to help the user quickly distinguish its features.
  • A utility can use animation, such as with the Find utility and ScanDisk.
  • A utility either does not include a toolbar or offers a simple toolbar using large buttons and text to describe the buttons. If the utility includes a toolbar, the toolbar shouldn't depend upon tooltips to explain its buttons.
  • If a utility supports advanced user interface features (such as keyboard shortcuts, context menus, and direct manipulation), those features should not be the only way to accomplish the task. Utility users are more likely to employ the more visible means of using the program.

Multiple-document interfaces are not suitable for utilities because they are just too complex for the simple, quick tasks performed by utilities. An MDI utility would force the user to manage too many windows; SDI and dialog box interfaces don't require this additional effort. This is at least one reason why Windows Explorer is a much better program than the old File Manager.

As explained in the last chapter, menus are more suitable for beginners than toolbars are because a menu is an excellent teaching tool, providing the user with context missing from toolbars. Note that few of the utilities that come with Microsoft Windows have toolbars. (I know, many of the Microsoft Windows NT Administrative utilities use toolbars, but these are clearly aimed at more advanced users.) If a utility does use a toolbar, the toolbar is usually quite different from an application toolbar. Far simpler and much larger, a utility toolbar includes only a few obvious commands with descriptive text and graphics.

click to view at full size.

Lastly, note that utilities can get away with nonstandard interfaces more easily than applications can. Since a utility is generally used in small doses, nonstandard buttons, graphic backgrounds, and bright colors are acceptable because these features won't be used long enough to grow tiresome.



Developing User Interfaces for Microsoft Windows
Developing User Interfaces for Microsoft Windows
ISBN: 0735605866
EAN: 2147483647
Year: 2005
Pages: 334

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net