29 lines
3.6 KiB
Plaintext
29 lines
3.6 KiB
Plaintext
# Garden of windows
|
|
|
|
Required by patterns Multiple settings, Command control center
|
|
May require patterns Zen garden, Rich garden, Organized desktop, Cooperating windows, Goal-oriented areas
|
|
|
|
...for each application within Multiple settings the user may be performing more than one distinct task at a time or may require several views of information in order to get the job done.
|
|
|
|
==> You need a way to partition these tasks into assimilable pieces so that the user is not overwhelmed. <==
|
|
|
|
Too much functionality and data clutters a window and will overwhelm the user with information. Lots of graphs, scrolling text, blinking icons and multiple views of the same data can give the user a headache.
|
|
|
|
A huge single window is a throwback to the days of screens and consoles. The applications tile the screen into areas of functionality. These areas may or may not be related. In single task applications, such as a text editor, this may be fine. But in multiple task applications, this will only clutter the single window. A user can only focus on one task at a time and should not be forced to mentally filter out data that is not relevant to that task.
|
|
|
|
In Netscape Navigator, a huge single window is used as the primary canvas for all web page content. In order to prevent the user from having to do page loads for additional windows, web pages are often broken up into poor man's windows: frames. This is a poor partitioning of tasks. They are still encapsulated by one window (the Navigator) and each frame begs for the user's focus.
|
|
|
|
Therefore:
|
|
|
|
==> Use a separate window for each distinct task and each unique view of data that is related to the same application. Label the window with the name of the task. <==
|
|
|
|
In an integrated development environment (IDE), such as Symantec Cafe, you have a collection of tools to help you develop an application. Each tool carries out a distinct task: managing projects, editing source files, compiling source files, debugging programs and running the resulting application.
|
|
|
|
These tasks can operate somewhat independently and that makes an IDE useful. The code can be edited in one window and the results viewed in another. The edit window is labeled with the name of the source file, so the user is reminded that the data displayed and the controls contained within the window are related to the task of editing a file. The output window is labeled ``Output'' to remind the user that the window contains information related to application results. At any time, the user chooses which window to focus on, while keeping them all close at hand.
|
|
|
|
A user may want to see data displayed in different ways. Therefore, it may be useful to display data in both tabular and graphical form. The tabular form displays exact values while the graphical form allows the user to see trends and patterns. An EKG display shows the exact pulse and blood pressure digitally, but also provides a display showing the heart rhythm.
|
|
|
|
Use Organized desktop to help determine how to arrange your windows. Use a Command control center to help manage the workspace, and allow for communication and organization between tasks through Cooperating windows. Each of these windows may consist of a Goal-oriented areas.
|
|
|
|
Too many windows will clutter the screen and may confuse the user. However, artificially limiting the number of windows in order to reduce clutter can reduce a user's productivity. For applications which are geared toward novices or have a small number of tasks to perform, consider building a Zen garden. For applications which require greater flexibility or configurability, and have more demanding users, consider a Rich garden...
|