Legal Notices
Hewlett-Packard makes no warranty of any kind with regard to this
manual, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be held liable for errors contained herein or direct, indirect,
special, incidental or consequential damages in connection with the
furnishing, performance, or use of this material.
Warranty. A copy of the specific warranty terms applicable to your
Hewlett- Packard product and replacement parts can be obtained from
your local Sales and Service Office.
Restricted Rights Legend. All rights are reserved. No part of this
document may be photocopied, reproduced, or translated to another
language without the prior written consent of Hewlett-Packard
Company. The information contained in this document is subject to
change without notice.
Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013
for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the
Commercial Computer Software Restricted Rights clause at FAR
52.227-19 for other agencies.
HEWLETT-PACKARD COMPANY
3404 E. Harmony Road
Fort Collins, CO 80528 U.S.A.
Use of this manual and flexible disk(s), tape cartridge(s), or CD-ROM(s)
supplied for this pack is restricted to this product only. Additional copies
of the programs may be made for security and back-up purposes only.
Resale of the programs in their present form or with alterations, is
expressly prohibited.
Copyright Notices. Copyright 1983-2000 Hewlett-Packard Company,
all rights reserved.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright
laws.
Contains software from AirMedia, Inc.
Contents
Contents
Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Temporal Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2. Web Applications
Introduction to Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Launching Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP OpenView Web Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Launcher Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Graphics Used in Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Launcher and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Launcher and Session Information . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
51
55
55
57
64
64
65
70
70
71
72
73
75
75
75
75
Contents
Contents
Menu Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Container Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General-Purpose Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menus for Managed-Object Functionality . . . . . . . . . . . . . . . . . . .
Sequence of Menu Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pop-Up Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Context and Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Registration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Number of Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Depth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cues for Types of Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Separators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Mnemonics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Accelerators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help on Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
119
120
122
125
126
127
128
129
130
131
132
133
134
134
135
136
Toolbar Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
When to use Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Content of Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Control and Support for Toolbar Use . . . . . . . . . . . . . . . . . . . .
Tool Buttons in the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Toolbar Structure and Customization . . . . . . . . . . . . . . . . . . . . . . . .
Context Control Within the Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . .
Context and Toolbar Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Registration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
137
137
137
138
139
140
141
141
141
Contents
Contents
200
200
200
204
205
206
207
207
214
217
217
217
221
221
222
222
223
224
225
227
10
Contents
11
Contents
12
275
275
275
276
276
276
277
278
278
278
279
279
279
280
280
281
282
284
Contents
13
Contents
14
307
307
307
309
309
310
311
311
312
312
313
315
316
316
317
318
319
320
321
322
322
323
324
325
325
327
329
331
333
334
Contents
15
Contents
16
Figure 2-1 . Launcher Window with the Task Tab Selected . . . . . . . . . .40
Figure 2-2 . Icons for Categories and for Leaf Level Items . . . . . . . . . . .45
Figure 2-3 . Web Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Figure 3-1 . Object Presentation Manager . . . . . . . . . . . . . . . . . . . . . . . .78
Figure 3-2 . Task Presentation Manager with a Task Presented in a
Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Figure 3-3 . Task Presentation Manager with Task Presented in a Tab
Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Figure 3-4 . Visual Cues and Task Completion Feedback in a Task
Presentation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Figure 3-5 . Related Task Tab in a Task Presentation Manager with a
Tab Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Figure 3-6 . Example of an Information Presentation Manager. . . . . . .87
Figure 3-7 . Multipurpose Presentation Manager . . . . . . . . . . . . . . . . . .89
Figure 4-1 . Scope Pane Window with Network Hierarchy . . . . . . . . . . .94
Figure 4-2 . Scope Pane Window with Categories to be Matched . . . . . .95
Figure 4-3 . A Multiple Pane Window . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Figure 4-4 . A Split Scope Pane Window . . . . . . . . . . . . . . . . . . . . . . . .100
Figure 5-1 . Window with Its Components Identified . . . . . . . . . . . . . .105
Figure 5-2 . Sequence for Items in Menu Bars Using OSI Menus . . . .115
Figure 5-3 . Sequence for Items in Menu Bars Using an Action Menu 115
Figure 5-4 . A Menu Bar Using Object-Based Menus . . . . . . . . . . . . . .115
Figure 5-5 . A Cascading Toolbar Button . . . . . . . . . . . . . . . . . . . . . . . .130
Figure 5-6 . Description Bar over the Scope and Results Panes in a
Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Figure 5-7 . Context List in a Close and Open State . . . . . . . . . . . . . . .135
Figure 5-8 . Context Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Figure 5-9 . Two Examples of Scope Panes Showing Hierarchies . . . .139
Figure 5-10 . Expansion Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
17
19
20
Tables
Table 2-1. Defined Color Usage for HTML Based Applications . . . . . . .56
Table 2-2. Defined Java System Color Variable Usage . . . . . . . . . . . . . .57
Table 5-1. Required Visual Cues for Menu Items . . . . . . . . . . . . . . . . .123
Table 6-1. Obsolete Symbol Types and Their Replacements. . . . . . . . .187
Table 6-2. Existing Symbol Class Shapes. . . . . . . . . . . . . . . . . . . . . . . .191
Table 6-3. Internal Graphics Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
Table 6-4. Visual Cues Used in Existing Graphics . . . . . . . . . . . . . . . .198
Table 8-1. Default Status Colors Defined for HP OpenView . . . . . . . . .245
Table 9-1. Recommended Dialog Box Title Formats . . . . . . . . . . . . . . .265
Table 9-2. Labels and Definitions for Push Buttons . . . . . . . . . . . . . . .280
Table 9-3. Guidelines for Showing Buttons as Unavailable . . . . . . . . .281
Table B-1. Common Accelerator Key Assignments in HP OpenView. .350
Table B-2. Common Mnemonic Access Key Assignments in
HP OpenView. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350
Table C-1. Color Values in the Limited Color Palette . . . . . . . . . . . . . .356
Table C-2. Color Values in the Expanded Color Palette . . . . . . . . . . . .358
21
Tables
22
Conventions
The following typographical conventions are used in this manual.
Font
Example
To provide emphasis.
Bold
Computer
Italic
/usr/bin/X11
Process names.
Computer
Bold
Keycap
Keyboard keys.
Press Return.
[Button]
Menu
Items
Select Edit:Find->Objects by
Comment
23
24
Contact Information
Technical Support Technical support information can be found on the HP OpenView World
Wide Web site at:
http://www.hp.com/openview/support.html
________________________________
Documentation
Feedback
Training
Information
25
26
27
28
Chapter 1
Overview
HP OpenView is a family of tools and services for managing the IT
infrastructure associated with a company. The tools and services in the
HP OpenView family cover management for desktop computers,
distributed systems, data, applications, local and wide area multivendor
networks, etc. HP OpenView provides tools for creating multivendor
system, network, software, and service management applications.
Applications are perceived by the user as being part of the HP OpenView
family, to the extent that they provide a common appearance and
behavior. This style guide provides a summary of the recommended
appearance and behavior for applications in the HP OpenView family.
Except where specifically indicated, the style recommendations are
applicable regardless of the technology on which the application is built
or the operating systems on which it is presented.
The style for HP OpenView products is in accordance with the general
principles in the The Windows Interface Guidelines for Software Design.
This guide is designed to:
Present a subset of the guidelines from The Windows Interface
Guidelines for Software Design that need emphasis or special
interpretation for products in the HP OpenView Family.
Introduce style guidelines that are unique to HP OpenView products.
Chapter 1
29
HP OpenView Vision
The platforms and applications that are part of the HP OpenView family
should strive to realize the following vision:
Multiple products look like one.
Product boundaries disappear.
Consistent style; looks and behaves the same.
Customer receives instant value.
Works right out of the box, with no modifications required.
Addresses real world problems.
Products work intuitively, while offering guidance.
Interactions match typical user expectations.
Users are guided through their activities.
Products are adaptable.
Customizable to fit user needs and their environment.
Extensible to match users changing needs.
30
Chapter 1
Chapter 1
31
32
Chapter 1
Chapter 1
33
Important Concepts
HP OpenView has a number of important concepts on which the user
interface style is based. These concepts are briefly explained in the
following sections.
Presentation Managers
Presentation managers are windows which present users with views of
managed objects, access to functionality for manipulating objects,
guidance in accomplishing tasks and/or a means of presenting
information on managed objects. Presentation managers are
distinguished from other windows in that they are designed to suit the
users needs and to minimize the number of windows that the user needs
to navigate through in order to accomplish their goals. Typically
presentation managers will allow the integration of other related
applications so that users can access necessary information for a given
management area or task from within a single window. Microsofts
Management Console (MMC) and Network Node Manager both provide
frameworks on which presentation mangers can be built.
HP OpenView provides a set of presentation managers into which
applications can integrate. These presentation managers provide
capabilities that can be used by integrating applications (for example,
NNM Network Presenter, Manage X). Integration into a presentation
manager can minimize the development effort required of the
integrating applications. For example, applications can use the discovery
and multiple selection capabilities of NNM and Manage X.
Developers can also choose to create their own independent presentation
managers.
See Chapter 3 , HP OpenView Presentation Managers for guidelines
regarding presentation managers.
Web Launcher
HP OpenView provides a web launcher into which applications can
integrate. The web launcher provides a single access point on the web;
from which the user can:
Start all HP OpenView web applications.
34
Chapter 1
Context
Context is an abstract concept which can be applied to the user interface
to filter the information that is presented and to provide a view of
information from different perspectives. Contextual information such as
who the user is, the user role, recent user actions, or events and alarms
can be used to filter the functionality and objects presented in the user
interface. This allows the user to focus on information that is relevant to
the current task. This same type of information can be used by
applications to vary the way information is presented. This enables the
information presentation to match the preferences and needs of the user
as he interacts with the management system. Sharing of contextual
information, allows independently developed applications to appear to
the user as highly integrated applications that work closely together.
Context can also be used to maximize user productivity. Contextual
information such as the currently visible view or recent user actions can
be used to set defaults that minimize the need for user input. This same
information can be used to filter irrelevant information or steps so that
users can more quickly reach their goals. By passing contextual
information between components within an application and between one
application and others, the need for the user to duplicate his actions is
minimized.
HP OpenView currently provides a number of components which support
the use of context to aid the user. These components are described in the
next six sections.
Chapter 1
35
Chapter 1
NOTE
View context is a very flexible concept and, in the future, could be used
for other purposes than menu item specification (that is, determining
whether a given object would appear in a view or accessing related views
containing a specified object).
Chapter 1
37
Groups
Groups contain arbitrary sets of objects and/or other groups. Groups can
be defined by applications or by end users. They have a variety of uses
such as:
Setting up security.
Allowing a user defined hierarchy of objects and relationships.
Allowing a user action taken at a group level to propagate down to all
the members of the group.
Grouping objects for viewing.
Grouping objects for selection, which:
Allows users to act on multiple objects at one time.
Provides a means of setting up a global selection list.
Further information and guidelines on groups are presented in Chapter
7 , Object Selections, Grouping, and Drag and Drop.
38
Chapter 1
Chapter 1
39
40
Chapter 1
Chapter 1
41
42
Chapter 1
Recommended
Chapter 1
43
44
Chapter 1
Web Applications
45
Web Applications
46
Chapter 2
Web Applications
Introduction to Web Applications
Chapter 2
47
Web Applications
Introduction to Web Applications
products as described in other chapters of this style guide. This chapter
discusses those areas that need special attention, given that an
application will be based on web technologies (such as HTML or Java).
48
Chapter 2
Web Applications
Launching Web Applications
Chapter 2
49
Web Applications
Launching Web Applications
Figure 2-1
Chapter 2
Web Applications
Launching Web Applications
area displays a short help message explaining the operation of the item
over which the pointer has been placed.
There are top level categories defined for each of the predefined tabs in
the launcher. These categories are presented in Appendix A , HP
OpenView Launcher Categories.
Launcher Registration
The HP OpenView Launcher allows for the integration of web
applications by means of a registration file. The entries in the
registration file determine the placement of the application entries
within the launcher.
Recommended
Recommended
51
Web Applications
Launching Web Applications
This will allow users that have a native-code product running locally
on the system to access all of the functionality that is available via
the web.
Required
New launcher registration entries must not add tabs beyond the
specified set.
The tabs are intended to group functionality in ways that make it easier
for users to access the functionality when they are using the different
approaches to management (Exception Driven, User Guided, and Task
Based), that are presented in User Approaches to Management in
Chapter 1 .
Recommended
New launcher entries should be defined so they fit within the predefined
launcher categories presented in Appendix A , HP OpenView Launcher
Categories.
Using the predefined categories will keep the launcher consistent and
will make it easier for users to find and access related functionality.
Recommended
Recommended
In the Object tab, launcher entries should be provided down to the level
of the context entries for presentation managers. Entries should NOT
be provided for views contained within the context.
For example, a network application should register a launcher entry for
the IP internet under the Network Views category but should not
register entries for the networks and subnets within the IP internet.
NOTE
52
Chapter 2
Web Applications
Launching Web Applications
Chapter 5 . For information on object presentation managers see Object
Presentation Managers in Chapter 3 .
Recommended
In the Task tab, entries should be provided for categories of tasks and the
tasks that users would want to do. Entries should NOT be provided for
subtasks within a task.
For example, an application that provides service management should
provide task entries for creating and modifying service level agreements
but should not include entries for modifying the service availability
parameters in the service level agreement.
Recommended
Entries made in the task tab should be stated in the form of a task.
For example, View Reports under Information Access and Reporting or
View OV Users under Security Management.
NOTE
It is a good idea to have the top level task categories on the task tab of
the launcher, correspond to items in the context button of a task
presentation manager. The applications entries into task tab of the
launcher should correspond to the tasks listed in the scope pane of the
task presentation manager. For more information on context controls see
Context Controls in Chapter 5 , for information on task presentation
managers see Task Presentation Managers in Chapter 3 .
Recommended
In the Tools tab, entries should be provided for applications and for the
tools provided by the application. Entries should NOT be provided for
each piece of functionality provided by the tool.
For example, the HP OpenView Network Node Manager should provide a
top level entry for the Network Node Manager application and lower
level entries for the Network Presenter, SNMP Data Presenter, and
Alarm Browser. Entries should not be provided for individual types of
information presented through the SNMP Data Presenter.
Chapter 2
53
Web Applications
Launching Web Applications
NOTE
It is a good idea to have the entries in the tools tab of the launcher
correspond to the separate graphical user interfaces provided by the
product.
Required
Applications must NOT provide entries for the Management Area tab.
This tab is intended to be configured by the HP OpenView administrator
to match the type of management that is anticipated to be done and to
provide quick access to frequently used capabilities.
Applications can provide commented out entries for the Management
Area tab to aid the HP OpenView administrator in setting up a tab that
would be focused on a given type of management. For example a service
management application could provide commented out registration files
to place views, tasks, and tools related to service management within a
single tab.
Required
Recommended
Required
All launcher entries are required to provide a help text string that
explains the operation of the launcher entry and the type of functionality
that is accessed by the entry.
Required
Applications registered in the launcher must set the locale for the
application based on the session locale set by the user. See HP OpenView
54
Chapter 2
Web Applications
Launching Web Applications
Integration Series: OpenView Windows Developers Guide for more
information.
Required
Leaf level items that provide application access from the launcher should
be include icons that represent the type of application functionality that
is being launched. See Figure 2-2, Icons for Categories and for Leaf
Level Items.
Figure 2-2
Recommended
Icons used in the launcher should follow the guidelines for symbols
presented in Chapter 6 , Objects and Symbols.
Chapter 2
55
Web Applications
Launching Web Applications
Network Administrator
This role is intended for individuals who have a higher level of
knowledge of the network, how it functions and how to trouble shoot
problems with the network. Applications that provide capabilities for
configuration of the network and major connecting devices should
specify this as their associated user role.
Network Operator
This role is intended for individuals who do routine trouble shooting
and maintenance tasks associated with the network. Applications
that provide capabilities for monitoring the network and routine
modifications to the network and network devices should specify this
as their associated user role.
NT Systems Administrator
This role is intended for individuals who have a higher level of
knowledge of NT systems, how NT systems function, and how to
trouble shoot problems with the systems. Applications that provide
capabilities for configuration of the NT operating system should
specify this as their associated user role.
NT Systems Operator
This role is intended for individuals who do routine trouble shooting
and maintenance tasks associated with computer running the NT
operating system. Applications that provide capabilities for
monitoring NT systems and routine modifications to the systems
should specify this as their associated user role.
UNIX Systems Administrator
This role is intended for individuals who have a higher level of
knowledge of UNIX systems, how UNIX systems function, and how to
trouble shoot problems with the systems. Applications that provide
capabilities for configuration of the UNIX operating system should
specify this as their associated user role.
UNIX Systems Operator
This role is intended for individuals who do routine trouble shooting
and maintenance tasks associated with computer running the UNIX
operating system. Applications that provide capabilities for
monitoring UNIX systems and routine modifications to the systems
should specify this as their associated user role.
56
Chapter 2
Web Applications
Launching Web Applications
HP OpenView Administrator
This role is intended for individuals who do configuration of HP
OpenView environment and management applications. Components
of management applications that are associated with configuration
and customizing of the management application should specify this
as their associated user role.
The file in which the user roles are specified is the htgroup file.By default
each of the preconfigured user roles is available to all users. This allows
the functionality to be accessed by all users until the HP OpenView
Administrator modifies the htgroup file to restrict access to specific
users.
Recommended
In the launcher registration file, applications should specify the user role
that would typically be associated with the users of the application.
The specification of the user role will allow the HP OpenView
Administrator to restrict access to the application if this is appropriate to
their application.
Recommended
The predefined user roles should be used whenever possible. Do not add
new user roles unless predefined user roles are inapplicable to the
application.
Recommended
If a new user role is defined in the htgroup file, the default specification
for the user role should contain the all wildcard (+) so that all user
logins can access the functionality. Only the HP OpenView
Administrator in the customers site should restrict the functionality
associated with applications.
Chapter 2
57
Web Applications
Launching Web Applications
Required
Applications must use the locale set by the user for the session.
See the The Integration Series: HP OpenView Windows Developers Guide
for information on how to access session information available from the
launcher.
58
Chapter 2
Web Applications
Use of Web Browsers
Java Applets
A Java applet can be presented either in a browser window or outside a
browser in a Java frame. Which method an applet uses is dependent on
the characteristics of that applet. The interaction style of an applet
presented within a web browser window is to some extent determined by
the web browser and the user settings within the browser. Presentation
of an applet in a Java frame provides more flexibility. However,
presentation of a Java applet in a Java frame can result in the
presentation of extraneous browser windows that must be kept around
in order for the Java applet to continue running.
Recommended
As more of the following criteria are met, the more appropriate it is for
the Java applet to be presented in a Java frame instead of inside a
browser window:
Users want to resize the window (for example, the application is
running over a long period of time, and information is presented in a
tree list that may expand).
Chapter 2
59
Web Applications
Use of Web Browsers
When Java applets are presented in a browser window, they stay a
constant size and do not change size when the user resizes the
browser window unless specific coding is done to enable the applet to
change size.
The applet has a large amount of functionality and will need to
present the user with a menu bar.
Java does not currently allow menu bars for applications presented
inside browser windows.
The set of applets that make up the application can be implemented
such that there is only a need for a single browser window to be
running in the users environment (not one browser window per
applet).
The applet presents all the necessary navigational controls inside it,
and there is no need for the navigational controls provided by the
browser.
There are numerous java applets running, and users may benefit
from having an application-specific title bar when a window is
minimized.
When running in a web browser window, the title bar always starts
with the name of the web browser and the name of the object being
acted on (but the name of the application may not be visible when the
window is minimized).
The applet is running in an environment where the majority of the
Java applets are running outside of a web browser window, and it will
be more consistent for the user to have all Java applets running in
their own windows.
Recommended
As more of the following criteria are met, the more appropriate it is for
the Java applet to be presented in a browser window instead of inside a
Java frame:
Users will have no need to resize the applet (for example, the user
interface is up for only a short period of time, and all information can
be presented in a small amount of space).
The applet has a limited amount of functionality that can be handled
via a toolbar or controls within the applet.
The applet will be running under conditions that will require a
browser window to be associated with each applet.
60
Chapter 2
Web Applications
Use of Web Browsers
Presenting the applet in the browser window will save a user from
having two windows on his desktop when only one is required.
The applet needs to use the navigational controls provided by the
browser.
There are few applications running in browser windows, and a user
will be able to easily identify each application window even when
they are iconified.
The applet is running in an environment where the majority of the
application functionality is provided inside a web browser windows,
and it will be more consistent for a user to have all Java applets
running in web browser windows.
Recommended
Optional
Provide a picture above the progress indicator to make the window more
visually appealing to the user.
Recommended
Chapter 2
61
Web Applications
Use of Web Browsers
Recommended
As more of the following criteria are met, the more appropriate it is for
the application to be presented in a browser window with full browser
controls:
A users primary job involves interacting with a variety of web
locations and unrelated applications that are accessed over the web.
The interface is used on a periodic basis to access information, but is
not considered a primary tool for accomplishing the users tasks.
The application is initially accessed from a web browser window with
full controls and the user would have no need to maintain the current
results of the web browser window when the new application is
presented, that is, the new application can overlay the contents of the
browser without interfering with the users tasks.
Recommended
As more of the following criteria are met, the more appropriate it is for
the application to be presented in a browser window with the browser
controls removed:
The application presents all the necessary navigational controls
inside the frames it uses, or the application has limited functionality
(for example, a single page of content) and no need for navigational
controls.
The application would take up less display space if it were presented
in a web browser window with the controls removed.
A users job primarily involves interacting with applications that do
not require the use of the web browsers location control for access (for
example, any necessary applications are accessed from a presentation
manager or from the HP OpenView Launcher instead).
The environment in which a user is working is one in which browsers
controls are extraneous, and their removal will benefit user task
performance.
The application is initially accessed from a web browser window
without controls and the user would have no need to maintain the
current content of the web browser window when the new application
is presented, that is, the new application can overlay the contents of
the browser window without interfering with the users tasks.
62
Chapter 2
Web Applications
Web Applications and Security
To protect both the user data and the network and system elements
being managed, web-based management applications should provide
security based on logins and passwords.
Recommended
For ease of use, users should only be required to log in once per session.
This login is recommended to be the one associated with the HP
OpenView Launcher.
A user should not be required to give a login name and password for
every new URL or application that he accesses on the web. Since the HP
OpenView Launcher provides a login for the user and then passes this
user information on to applications, this should be the primary
mechanism for controlling access to web applications. See Launching
Web Applications earlier in this chapter for more information on the HP
OpenView Launcher.
Chapter 2
63
Web Applications
General Guidelines for Web Interfaces
Recommended
Recommended
Recommended
64
Chapter 2
Web Applications
General Guidelines for Web Interfaces
All names should start with OvWww.
Names should only contain alphanumeric characters.
Note: Spaces are not allowed.
Each new word in a name should begin with a capital letter.
Names should be related to the application or the presentation
manager that will be presented in the window.
Examples of named windows include:
OvWwwSnmpData
OvWwwHelpWindow
Recommended
Recommended
Chapter 2
65
Web Applications
General Guidelines for Web Interfaces
Recommended
Do not change the color of text that is presented in the main area of the
application. Users will have trouble reading the text if there is
insufficient contrast between the background color and the color of the
text.
Required
Table 2-1
Color
Name
Hexadecimal
Value for Color
white
#ffffff
black
#000000
navy
#000080
lightsteelblue
#c0c0ff a
lightgrey
#c0c0c0
lightyellow
#ffffe0
lightblue
#add8e6
green
#00ff00
1) Normal status
red
#ff0000
1) Critical status
66
Chapter 2
Web Applications
General Guidelines for Web Interfaces
Table 2-1
Color
Name
Hexadecimal
Value for Color
yellow
#ffff00
1) Minor status
orange
#ff8000 a
1) Major status
cyan
#00ffff
1) Warning status
ivory
#ffffcc a
1) Unmanaged status
lightblue
#0080ff a
1) Unknown status
darkred
#640000 a
1) Disabled status
lightpink
#ff80ff a
1) Acknowledged status
tan
#ffbf66 a
1) Testing status
a. Hexadecimal values are different than the named colors for browsers.
Recommended
Java applets and applications should use the Java System Color
Variables for setting the color of interface components. See Table 2-2 for
specific recommendations.
Use of the System Color Variables will enable an applets to appear as an
application running natively on the client system.
Table 2-2
System Color
Variable Name
background
None
activeCaption
Chapter 2
67
Web Applications
General Guidelines for Web Interfaces
Table 2-2
System Color
Variable Name
activeCaptionText
activeCaptionBorder
None
inactiveCaption
inactiveCaptionText
inactiveCaptionBorder
None
window
windowBorder
None
windowText
menu
menuText
text
None
textHighlight
None
textHighlightText
None
textInactiveText
68
Chapter 2
Web Applications
General Guidelines for Web Interfaces
Table 2-2
System Color
Variable Name
control
controlText
controlHighlight
None
controlLtHighlight
controlShadow
controlDkShadow
None
scrollbar
1) Scrollbar
info
None
infoText
None
Recommended
69
Web Applications
General Guidelines for Web Interfaces
Displaying patterns adds clutter to the display and distracts the user
from his intended task. Many background patterns also detract from the
legibility of any text presented in the display.
Using Fonts
If an application manipulates the fonts on its web pages, keep in mind
that not all systems have the same fonts.
Recommended
Recommended
Do not change the font size for most text presented in the display. This is
especially true for extensive text that users will need to read.
Users may have their font sizes set to meet their individual preferences
or abilities. For example, users who have vision difficulties may
intentionally set an applications fonts to larger sizes so they can more
accurately see the information that they are trying to read.
Recommended
If the font size for text presented in the browser is changed, it should be
done relative to the default font size rather than by setting an absolute
font size. Setting font size relative to the default allows users to maintain
control over the font size they are viewing (for example, <FONT
SIZE="-2">).
Optional
The font size of controls or buttons used in the screen can be set to allow
them to adequately fit in the display.
Use images on a web page only if the presentation of the image will
improve user performance over the presentation of simple text alone.
Images can lengthen the time to load a web page. In addition, too many
non- specific images can add clutter to the display and make it difficult
for a user to understand how to accomplish his tasks in the application.
70
Chapter 2
Web Applications
General Guidelines for Web Interfaces
Extraneous images with words like NEW and Hot have no place on
application web pages.
Recommended
Keep the size of displayed images small both in overall display size and
in file size.
Larger images take longer to load than smaller images. They also take
up display space. When running an application in a web browser, display
space is at a premium as the web browser already takes up a large
amount of the usable display space.
Recommended
Recommended
Provide users with clear visual cues to indicate which images or portions
of an image have a link associated with them. Visual cues that users will
associate with links include the following:
Presenting the images as three-dimensional controls that are similar
in appearance to push buttons in regular application windows.
Making any portions of images with links appear to be raised above
the rest of the image.
Presenting a band around the image that has the color used in links.
Recommended
Do not use animated graphics or flashing images unless they are used in
accord with the guidelines for flashing discussed in Chapter 8 , Visual
Presentation.
Scrolling
Recommended
Chapter 2
71
Web Applications
General Guidelines for Web Interfaces
necessarily meaningful to eliminate scrolling of the information. In such
cases where scrolling cannot be completely eliminated, the recommended
approach is to view the screen from the point of view of the user and the
type of task that he is doing.
Recommended
Make the most important information highly visible, and provide visual
cues for accessing information that is currently not visible. Minimize the
number of steps that a user must take to make the hidden information
visible.
Even if content must be scrolled, a user should not need to scroll
backward or forward in the window to access the primary controls.
Recommended
Navigating
The way users expect to navigate within an application is not the same
as when they are browsing for information on the web. User experience
with applications has led them to expect tightly controlled navigation
based on their tasks. User experience with browsing for information on
the web has led them to expect navigation based on links and the
sequence in which they have accessed these links.
In a web-based application, users can benefit from having both the
tightly-controlled application navigation presented in the application
space and sequential navigation presented through web browser
controls. To make this strategy work well, adhere to the following
guidelines.
Recommended
Make sure that navigation via the browsers [Back] button leads to the
locations that would be anticipated by a user. Information that is not
part of the main interaction with the application should be presented in
a separate window.
A user will likely become frustrated when the [Back] button takes him
to help text or an error message when he was anticipating the previous
page in the application.
72
Chapter 2
Web Applications
General Guidelines for Web Interfaces
Recommended
Recommended
NOTE
When the information is updated, for example, the user reloads the web
page or the application automatically reloads information, the
timestamp should be updated.
Recommended
Chapter 2
73
Web Applications
General Guidelines for Web Interfaces
It is recommended that this information be maintained via server push
mechanisms, which allow for faster presentation of a pages subset.
Recommended
74
Chapter 2
Web Applications
Web Applications Based on HTML
Using Frames
Frames make use of the features of web browsers to structure an
applications functionality to better match the structure applications
which are presented outside of web browsers. The frames can be used to
provide a separation between the application and the web browser, to
keep user controls constantly visible, and to provide a quick-access
mechanism for navigating to different capabilities provided by the
application.
Recommended
Recommended
Using Tables
Recommended
Recommended
75
Web Applications
Web Applications Based on HTML
Recommended
Using Forms
Forms are the typical method for collecting user input in an HTML based
application. The guidelines for the design of forms in HTML are the
same as those for the design of dialog boxes when using Java or C++. See
recommendations in Chapter 9 , Dialog Boxes and Controls, for
guidelines for how to design forms.
Recommended
If a user is not required to fill in all fields on a form before submitting it,
the [Apply] or [OK] button should be visible from all locations in the
form.
76
Chapter 2
Web Applications
Components of Web Applications
Title Bar
Required
Recommended
The title bar should use the colors specified in Table 2-1, Defined Color
Usage for HTML Based Applications, or Table 2-2, Defined Java
System Color Variable Usage.
Chapter 2
77
Web Applications
Components of Web Applications
Recommended
The size of the title bar area should be approximately 30-40 pixels in
height, and it should extend across the entire page.
Recommended
Graphics can be presented in the title bar if they will help identify the
application. These graphics should be no more than 24 pixels in height.
Recommended
The label in the title bar will depend on the style of window that is being
presented in the web browser, how the page was accessed, and whether
the contents of the window are associated with a single object or multiple
objects. Follow the recommendations in Chapter 5 , Window
Components, for the format and content of the title bar.
Context Area
Required
Recommended
The context control should be presented in a small frame on the left side
of the toolbar directly beneath the title bar, or as a control within the
toolbar.
Recommended
Toolbar
Since there is currently no way to present a pull-down menu in an
application presented in a web browser, most functionality associated
with the web application should be presented in a toolbar frame or in tool
buttons in the results pane. The toolbar in the web browser, unlike the
toolbar in an application window, is not simply a quick-access
mechanism. It may be the only method for accessing functionality.
78
Chapter 2
Web Applications
Components of Web Applications
NOTE
Recommended
Recommended
Recommended
The default location for the toolbar should be directly below the title bar.
It is beneficial to allow users to configure the toolbar to be in a different
location.
Recommended
Only display toolbar buttons in the toolbar frame which are applicable to
the current context.
Following this guideline will minimize the number of controls presented
in the toolbar at any one time.
Recommended
Provide visual cues for the toolbar buttons to make it clear to users that
they can be clicked on for accessing functionality.
Visual cues that can be used to inform users that the toolbar images
access functionality include:
Providing tool tips that indicate the functionality that can be accessed
by the button.
Making the images change on mouse over so that it is clear that they
can be activated, this is similar to the visual cues provide in the
Netscape and Internet Explorer Browsers.
Giving the images in the toolbar a three-dimensional appearance so
that they appear to users as if they can be pressed.
Providing a label for the image that is underlined. Since hyperlinks
Chapter 2
79
Web Applications
Components of Web Applications
are typically underlined, the underlining of the label will indicate to
the user that the image and label are a link to some other
functionality.
Recommended
Recommended
Recommended
To aid users in recognizing and learning to use the tools in the toolbar,
use one of the following mechanisms:
Include labels under the toolbar buttons to define the functionality
that will be accessed by clicking on the button.
Provide pop-up messages that appear when the pointer moves over
each toolbar button.
These pop-up messages can be provided by specifying alternative text
associated with each of the images.
Provide active help in the status area of the same window that
contains the toolbar. The active help should change as the pointer
moves over the various images in the toolbar.
Required
80
Chapter 2
Web Applications
Components of Web Applications
Scope Pane
The scope pane is on the left side of the page under the context control
and toolbar. Items presented in the scope pane should provide users with
links to different sets of information that can be presented in the results
pane.
Recommended
Recommended
The scope pane should be presented in a separate frame to the left of the
results pane.
Required
Recommended
If a user changes the current context by means of the context control, the
scope panes contents should also change to match this new context
setting.
Required
Recommended
Chapter 2
81
Web Applications
Components of Web Applications
Recommended
The location cursor in the scope pane should be indicated by one of the
following:
A black rectangle outlining the item that the location cursor is on.
An arrow pointing at the items icon or label and which is placed to
the left of the label.
Results Pane
The results pane is the area used for presenting both any managed
objects and the main functionality of the application.
Recommended
When a user first enters the application window, the results pane should
not be empty. If there is a scope pane in the window, the results pane
should present the information associated with the first link in the scope
pane or the last link that the user accessed within this application
context.
Recommended
Recommended
82
Chapter 2
Web Applications
Components of Web Applications
Figure 2-3
Web Application
Chapter 2
83
Web Applications
Components of Web Applications
Control/Status Frame
The use of a control/status frame is optional for HP OpenView web
applications.
Recommended
Recommended
84
Chapter 2
HP OpenView Presentation
Managers
85
86
Chapter 3
Required
Required
Chapter 3
87
Recommended
Figure 3-1
88
Chapter 3
Chapter 3
89
Required
Required
Recommended
The task presentation manager should present the task as a wizard that
guides the user through the task using next and previous buttons when
one or more of the following are true:
The task involves a set of steps or subtasks that the user must do in a
proscribed sequence to successfully complete the task.
The task involves a set of steps or subtasks and users must complete
each step or subtask to successfully complete the task.
Users do the task infrequently and will need guidance to complete the
task.
Creation and initial configuration are examples of tasks that are best
presented in a wizard. See Figure 3-2 for an example of a task presented
in a wizard inside a task presentation manager.
Recommended
The task presentation manager should present the task in a tab control
where the user can choose what tabs they want to access and modify
when:
90
Chapter 3
Recommended
91
Recommended
When a user has started a task in the task presentation manager but has
not completed it before starting a new task in the same presentation
manager:
The users should be given a means of reaccessing the partially
completed task at a later time without the loss of entered data.
or
Before the initial task is overlaid, the user should be presented with a
confirmation dialog box indicating that the data will be lost if the user
chooses to proceed with the new task.
Examples of mechanisms for reaccessing the partially completed task
would include the use of navigation tabs (see Navigation Tabs in
Chapter 5 ) that allow access to the task (see Figure 3-4) or providing a
back button that would take users back to the screen with the partially
completed data.
92
Chapter 3
Recommendation
When there has been a change of state in an ongoing task, that is not
currently visible in the task presentation manager, there should be a
visible indication to the user of the change in state. When navigation
tabs are provided:
A check mark on the left side of the navigation tab is recommended as
a visual indicator that the task was successful or there is a change in
state that does not include an error.
An exclamation mark in the appropriate status color (red=critical,
orange=major, yellow=minor) is recommended as a visual indicator
that there is a change in task status that includes an error.
Providing a visual indication of a change in state, notifies the user that
they should return to the task to determine what has happened. In the
example in Figure 3-4, the check mark in the navigation tab is indicating
that the installation of the software have been completed.
Chapter 3
93
When the user takes an action that successfully completes a task within
the task presentation manager and the wizard or proprieties box is not
removed, a message must be given that indicates that the task has been
successfully completed.
Required
Recommended
If a task presented in a tab control has related tasks that the user may
want to do after finishing the initial task, all guidelines below should be
followed:
The last tab in the tab control should present users with information
on the related tasks and a means of accessing the functionality to do
the related tasks.
In the Related Tasks tab, visual cues should be provided that allow
differentiation between related tasks that are optional and related
tasks that are required but may be deferred until a later time.
Related tasks that are required should be indicated by the word
(Required) in parentheses following the task name. Related tasks
that are optional should be indicated by the word (Optional) in
parentheses in following the task name.
If there are related tasks that are required for the user to achieve the
most likely goals of the initial task, the related task tab should
automatically be presented to the user at task completion, instead of
a completion message.
Immediately taking users to the related task tab instead of giving a
completion message when related tasks are required helps prevent user
errors. When users are new to an application or when they do tasks
94
Chapter 3
NOTE
Related tasks that are required and which cannot be deferred to a later
time should be presented as steps in the tab control or wizard.
Figure 3-5
Chapter 3
95
96
Chapter 3
Recommended
Chapter 3
97
Required
Recommended
Recommended
98
Chapter 3
Recommended
Chapter 3
99
Required
100
Chapter 3
Using Windows
This chapter covers the following topics:
Types of windows that can be used in HP OpenView applications and
guidelines on when to use each type.
101
Using Windows
102
Chapter 4
Using Windows
Windows in the HP OpenView Environment
NOTE
Chapter 4
103
Using Windows
Windows in the HP OpenView Environment
user steps, as multiple locations at different levels in the hierarchy are
simultaneously visible and accessible. See Figure 4-1.
Scope pane windows that present categories of information allow the
user to select multiple categories and to see data from the combination of
these categories in the content pane. The categories act somewhat like a
filter and allow users to quickly see different amounts of information.
See Figure 4-2.
Figure 4-1
104
Chapter 4
Using Windows
Windows in the HP OpenView Environment
Figure 4-2
When to Use
Recommended
Chapter 4
105
Using Windows
Windows in the HP OpenView Environment
Information on a hierarchy of managed objects or object components
(for example, reports on managed objects).
Information that can be grouped or categorized (for example,
messages or events associated with managed objects).
Online help information that has a hierarchy of topics or set of
related topics.
Sets or groupings of tasks that can be categorized and presented to
the user.
Sets of functionality that can be categorized and presented to the user
in a meaningful hierarchy.
Recommended
Multiple pane windows should be used only for complex activities where
the user needs to carry out multiple types of activities simultaneously
and the panes are needed to separate different types of information (for
example, navigation, controls, or summary information).
106
Chapter 4
Using Windows
Windows in the HP OpenView Environment
Figure 4-3
Chapter 4
107
Using Windows
Split Windows
Split Windows
Split windows are windows in which the number of panes being
displayed can change, based on actions taken by a user.
Recommended
If a scope pane window can be split and if the contents of the split results
pane can be associated with different items in the scope pane, implement
all guidelines below:
Both the results pane and the scope pane should be split horizontally,
so that there are two scope panes and two results panes.
If there are context tabs, they would be presented in each of the two
scope panes.
If there are navigation tabs, they would be presented in each of the
two results panes.
Navigation and context tabs have visual cues that make them appear
to be attached to the window contents. This may confuse users if the
tabs are not contained within the pane in which they will change the
information. See Figure 4-4 for an example.
Recommended
If a scope pane window can be split but the contents of the split results
pane can only be associated with a single item in the scope pane, only the
results pane should be split.
Splitting only the results pane maximizes the amount of display space
used for viewing the object, tool outputs, data set, or task.
Recommended
Recommended
If the mechanism for requesting the splitting of the window does not
108
Chapter 4
Using Windows
Split Windows
allow a user to specify what goes in the new pane, the split should result
in the presentation of the same information in both halves of the split.
Split controls in the scroll bars and a pull-down menu item for Split are
examples of mechanisms that do not allow users to choose what
information is to be presented at the time they split the window.
Recommended
Recommended
In a split window, the contents of the menu items, toolbar items, and
context list should be determined by the pane that is active (has the
focus).
Having the menu and toolbar items tied to the context of the active pane
is intuitive for users. Different panes within the window are made active
by clicking in the pane. When a user selects an object within a pane, it
should make the pane active and set the menu context to the view in that
pane. This will result in a set of menus that is tailored to the objects
within the active view.
In Figure 4-4, the top scope and content pane are currently active. The
menu bar and toolbar are specific to this pane. Users can use the context
control to change the navigation hierarchy for one of these panes and
leave the context for the other pane unchanged.
Recommended
The active pane of a split pane window should provide visual cues to the
user to indicate that it is the active pane.
Examples of visual cues to indicate that a pane is active include a black
box surrounding the active pane or a more brightly colored selection
cursor.
Chapter 4
109
Using Windows
Split Windows
Figure 4-4
110
Chapter 4
Using Windows
Creating New Windows
Recommended
Recommended
Recommended
Recommended
111
Using Windows
Creating New Windows
For example, an application presents detailed information on objects in a
separate window. This allows users to simultaneously view the status of
various managed objects as well as the details for just a single object.
The first time that the user requests details on a specific object
(Object A), a new window pops up to present the detailed information.
When the user requests details on a different object (Object B), the
detailed information on Object A is replaced with the information on
Object B.
Recommended
112
Chapter 4
Window Components
113
Window Components
114
Chapter 5
Window Components
Identification of Window Components
Chapter 5
115
Window Components
Title Bar
Title Bar
The title bar provides the user with a means for distinguishing different
windows that may be presented on the desktop. It also provides
contextual information to inform a user of his location within the
application. When an HP OpenView application window is presented
within a web browser, it provides the user with a visual cue (the title bar)
that separates the application window from the web browser and its
controls.
Required
Recommended
object,_tool,_task,_item
application_name
window_id
object, tool, task or item: This entry is intended to provide a user with
information that is related to where he is within the
application and what he is currently doing. As the user
navigates within the window and changes the
information presented in the window, this field within
the title bar should change to match the current
location in the window:
If the results pane of the window is related to a
single object, that objects name should appear in
116
Chapter 5
Window Components
Title Bar
this field (for example, as in an object presentation
manager).
If the results pane of the window is displaying a set
of data, the name for the data set should appear in
this field (for example, as in an information
presentation manager).
If the results pane of the window is presenting a
task, the tasks name should appear in this field (for
example, as in a task presentation manager, dialog
box or wizard).
application name: The application name is required in the title bar
because there are typically multiple applications
running in an HP OpenView environment. If a user
encounters a problem or needs to access
documentation, he will need to know which
applications documentation to read. To save space, it is
recommended that the application name be presented
in abbreviated format. Examples of application names
presented in abbreviated format are NNM, ITO, and
ITA.
window id:
Chapter 5
117
Window Components
Title Bar
An example of a title bar for a task presentation manager where the
current tasks is setting up a new alarm would be this:
118
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
Recommended
Recommended
Chapter 5
119
Window Components
Menu Bar and Pop-Up Menus
for opening other containers of the same type and general functionality
(such as printing). Examples of container menus are File, Map, Browser,
and Process.
Required
Required
All application windows must have a Close menu item in the first menu
in the menu bar (for example, File:Close or Map:Submap->Close).
Recommended
The name for the container menu should be chosen to reflect the types of
managed objects being presented and whether or not the managed
objects are contained in files.
In a context that presents network objects, for example, the name of the
container menu could be Map or Network. Other examples for this menu
might be Processes (for a process management application) or Circuits
(for an application that is used for building event correlation circuits). In
applications that deal with files, it is recommended that the name of the
container menu be File.
Recommended
120
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
When providing the general functionality that is not specific to a type of
management, present the functionality under the appropriate generic
menu bar label as described below.
Edit
Use for menu items that edit the content of the current
location in the managed object hierarchy and the
properties of managed objects. The Edit menu can also
contain menu items that allow the user to locate
symbols, objects, or locations within the application.
Examples of menu items to be presented under this
menu include New, Cut, Copy, and Paste.
View
Use for menu items that affect the way the current
data is presented. The View menu does not contain any
option that alters the data itself. Examples of View
menu items are Toolbar, Pan and Zoom, and
Presentation Formats.
Options
Help
Use for menu items that allow for access to online help
information, application documentation, version
information, and tutorials.
Tools
Window
Chapter 5
121
Window Components
Menu Bar and Pop-Up Menus
View menu. When scope pane windows are used, there
is no need for this menu and it is recommended that it
not be used.
Recommended
If menu item only allows the user to add specific managed objects, place
the menu item under the Edit menu and label this item in a way that
will allow users to know the types of objects they can add.
For example, in a window in which the user can only add users, the label
for the menu item should be New User, not New Object.
Required
Recommended
Required
Required
The Help menu must contain the following menu items: Overview,
Tasks and About.
Recommended
The Help menu should contain Online Manual and Glossary menu
items.
Optional
122
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
an Action menu. Which of these two alternatives is most appropriate for
your applications functionality is dependent on the functionality being
provided, types of objects that are being managed, the homogeneity of
the objects that are presented at any given level within the management
hierarchy, and the variability in the types of functionality being made
available to users.
Recommended
Recommended
123
Window Components
Menu Bar and Pop-Up Menus
modify configuration settings associated with managed
objects.
Fault
Accounting
Security
The Action menu provides a single location for all functionality which
act on the managed objects in the current window. This menus contents
may vary as a function of the level in the managed object hierarchy and
the currently-selected item. But, because variation in the content of the
menus is limited to specific menus (that is Action and Tools), users
quickly learn about the variable nature of these menus.
Action
Required
Recommended
If there is both an Action and an Edit menu, the Action menu should
not include items associated with editing, adding, deleting, copying. Put
these items under the Edit menu instead.
Some applications only have a small number of different types of objects
to present within their window or navigation hierarchy. These
applications can use either an Action menu or an object-based menu in
the menu bar.
<objectname> If an application window presents only one or two
specific types of objects, and they have a limited
number of menu items, use object-based menu items in
place of the Edit and Action menus.
124
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
Examples of object-based menu items can be Printers
and Queues (see Figure 5-4).
Recommended
Recommended
Recommended
Figure 5-2
Recommended
If a menu bar uses an Action menu to replace the OSI category menus,
the sequence items in the menu bar should be the same as shown in
Figure 5-3:
Figure 5-3
Recommended
If a menu bar uses one or more object menus to replace the Edit menu
and OSI category menus, all object menus except the container should be
presented before the View menu. In Figure 5-4, the object menus
appearing before the View menu are Printers and Queues.
Figure 5-4
Chapter 5
125
Window Components
Menu Bar and Pop-Up Menus
Pop-Up Menus
Menu items in pop-up menus are presented when a user clicks the menu
button on the pointing device. These menus are sometimes referred to as
context menus.
Required
Recommended
Recommended
Recommended
Optional
If a menu item acts on the symbol only and does not affect the object
associated with the symbol, it may appear on the pop-up menu only.
Recommended
For guidelines on the pop-up menu for symbol alerts, see Symbol Alerts
in Chapter 8 . Pop-up menus should provide access to the properties of
an object by means of a Properties menu item; this item should be the
last one in the pop-up menu.
Recommended
Pop-up menus should not contain grayed menu items. If a menu item is
temporarily unavailable, it should be removed from the pop-up menu.
NOTE
126
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
temporarily unavailable menu items is primarily a learning aid.
Experienced users do not require this learning aid, and it detracts from
the performance benefits of keeping the pop-up menus short.
Items in the menu bar must be consistently maintained across all levels
in an object hierarchy. New menu items should not appear as a result of
navigating to a lower level in the hierarchy, nor should existing menu
items be removed.
Required
With the exception of the Tools and Action menus, menu contents must
be consistently maintained across all levels in a hierarchy. If a menu
item is temporarily unavailable because of the set of items currently
displayed in the results pane or because of the current selection, this
menu item should be grayed rather than being removed from the menu.
Research shows that users become confused when menu items appear
and disappear from the menus. Having a menu item visible, but grayed,
lets users know where they need to go to access this functionality; it also
provides a visual cue to indicate that users must change the state of the
application in order to access the menu item.
NOTE
Restricting the changing menu items to the Action and Tools menu
will minimize learning difficulties for users. Experience across HP
OpenView applications and applications integrated into Microsofts
Chapter 5
127
Window Components
Menu Bar and Pop-Up Menus
MMC will train users to expect menu items in these menus to be
variable.
Recommended
Required
Optional
Menu bar items, as well as the contents of menus, may be changed when
a user changes to a different context via the context control in the
toolbar.
Recommended
NOTE
128
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
In addition to the guidelines on context and menu items presented above,
follow the guidelines below when specifying the menu structure for
pull-down menu items and pop-up menu items in application
registration files.
Recommended
Specify placement rules for Help menu items which match the placement
rules associated with the functionality that the help is describing. This
creates more context-specific help and to have it presented in the
appropriate submaps.
Optional
Recheck the view context for the hierarchy of views where menu items
will be placed. If the views do not have sufficient context identifiers to
handle the specificity of the menu items, add context identifiers.
Required
Menu Structure
Changes to the menu structure of an application across releases can be
disruptive to the performance of the operators of the application in that
it will necessitate retraining. Therefore, it is best to define an
applications menu structure to handle its full functionality even though
not all of the functionality is provided in a given release.
Recommended
Chapter 5
129
Window Components
Menu Bar and Pop-Up Menus
For example, the initial release of an application may include the items
noted as Release 1 below, while the items noted as Release 2 are planned
for, but not included in the initial release:
Defined Menu Structure
Release #
Systems:
Change Password
Add
Delete
Set Network Access
2
1
1
2
Number of Items
The number of menu items within a menu panel can either enhance
user-task performance or it can interfere with performance. Using a
menu is a search task where the user is searching to find the item that
will provide the functionality that they need to access. Search
performance is aided by minimizing menu depth and by providing visual
and cognitive cues to aid the user.
Recommended
Menus at a given level should contain between two and fifteen menu
items (eight is optimal).
Required
Recommended
If a menu will be created with only one or two menu items in it, consider
moving the menu items to a higher level in the menu structure (but not
into the menu bar).
If possible in an application, use an approach similar to that provided in
the Network Node Manager menu bar where menu cascades with a
single menu item are pulled up to the menu level above.
130
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
For example:
Configuration: Backup ->
Schedule
becomes
Configuration: Backup: Schedule
Menu Depth
Recommended
NOTE
If necessary to avoid menu clutter, pull-down menus can have a 4th level
of depth, but they should never have 5 levels.
Recommended
Chapter 5
131
Window Components
Menu Bar and Pop-Up Menus
Object
Menu Labels
Recommended
Choose a label for each menu item that clearly indicates the type of
functionality the menu item leads to and the extent of the items actions.
Where ambiguity could arise, use a label to indicate if the function acts
on all objects or a subset of objects, a single symbol, or the actual
resource being managed. For example:
Delete -> From This Submap
From Multiple Submaps
NOTE
Recommended
If a menu item does not provide clarification of the scope of its action, the
scope should be set to just the current object/symbol in the current
context. It should not affect all instances of the object in all contexts.
132
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
Provide cues on each menu label about the type of menu item. The cues
presented in Table 5-1 should be standard across all menu items in the
HP OpenView environment.
Table 5-1
Cue
Explanation
Unavailable
gray label
Dialog box
...
Chapter 5
133
Window Components
Menu Bar and Pop-Up Menus
Table 5-1
Cue
none
->
- Applicationb
Cascading
Explanation
a. Command menu items result in the direct execution of an action, such as Print.
b. Application menu items result in the direct presentation of an application window, such as
SNMP Configuration.
Menu Separators
Menu separators are lines drawn across the menu that act to separate
menu items from one another. When overused, menu separators can add
visual noise to the menus and can have a negative affect on user
performance.
Recommended
Menu Mnemonics
Menu mnemonics are designators that allow a user to move the selection
cursor to a menu item through a keyboard mechanism. A mnemonic is a
single character which is contained in the label for the menu item and
which supports ease of learning and use.
When the location cursor is within a menu or a menu bar, pressing the
mnemonic key for a menu item within the menu moves the location
cursor to that item and activates it.
The following are guidelines for the use of mnemonics in menus.
134
Chapter 5
Window Components
Menu Bar and Pop-Up Menus
Required
Required
Mnemonics for menu items that are added into an existing menu
structure should be chosen so they do not conflict with the mnemonics for
any existing menu items.
Recommended
Required
Required
Menu Accelerators
If an application uses keyboard accelerators, follow the guidelines for the
platform on which the application will be delivered.
Recommended
Recommended
Recommended
Recommended
NOTE
135
Window Components
Menu Bar and Pop-Up Menus
encountered by NNM will use the defined accelerators. These
accelerators will be invalid in the other applications that use them.
Recommended
Recommended
Recommended
In the help text for menu items, indicate what functionality is supplied
by the menu item, the types of objects on which the menu item acts, the
conditions under which the item is unavailable, and any other relevant
information.
136
Chapter 5
Window Components
Toolbar Guidelines
Toolbar Guidelines
The toolbar is a set of graphic controls. It provides quick access to
functionality that is already available to the user by other methods. It
may give the user access to frequently used menu items and tools, may
provide navigation shortcuts, or may enable the user to change the
presentation format of data. Toolbar access can simplify the number of
steps needed to perform common operations.
Toolbars can be statically attached to the window in a single location, or
they can be designed like dockable tool palettes (where they can be
detached from the window border, float within the window, and be
dismissed when they are no longer needed).
Applications should add tools to the standard toolbar if these tools will
improve usability by enhancing user access to common operations. For
example, an application which provides a new presentation format for a
view of managed objects should add this presentation format to the
standard toolbar.
Recommended
Provide dockable toolbars for times when a user will benefit by having
quick access to a set of capabilities to use over a period of time and then
dismiss when he goes on to other activities. Applications which provide
several large menus can improve their usability by providing quick
access to frequently used menu items via a dockable toolbar.
Content of Toolbars
Toolbars are intended only for frequently accessed functionality, not for
all of the functionality in an application. Dockable toolbars can be more
extensive since a user can choose different sets of tools and dismiss them
when he has finished using them.
Recommended
Chapter 5
137
Window Components
Toolbar Guidelines
frequently used functions in the toolbar. Make toolbar buttons
unavailable or remove them when they are no longer applicable to a
given view or selection.
Recommended
Make sure the functionality in the toolbar is also available through the
pull-down menus. When the standard toolbar is turned off or the
dockable toolbars are dismissed, the user will need another mechanism
for accessing the functionality provided in the toolbar.
Recommended
Recommended
If a history is kept of the views that are presented in the results pane of a
window, provide users with a [Back] button in the standard toolbar so
they can quickly access the last ten views that they visited.
Recommended
If an application uses dockable toolbars, provide tool buttons for all of the
major capabilities that users will want to access when doing their tasks.
The default location for the toolbar should be directly below the menu
bar. It is desirable to allow users to move toolbars and to dock them at
any border within the window to which they are attached.
When toolbars contain only graphic representations of objects, it can
sometimes be difficult for users to associate the graphics with the
functionality that they represent. Also, when items are presented only
graphically, they cannot be made accessible to the visually impaired via
accessibility software.
Recommended
To aid users in recognizing and accessing the tools in the toolbars, use
one of the following mechanisms:
Provide pop-up messages or tool tips that pop up when the mouse
pointer rests on the tool button.
In the windows status bar present context sensitive active help for
the toolbar button currently under the pointer.
Include labels under every graphic to indicate what they represent.
Caution should be used in providing labels under icons. If the label is
138
Chapter 5
Window Components
Toolbar Guidelines
part of the graphic, the graphic will need to be redrawn in order to be
localized.
Recommended
Enable users to hide the toolbar. While the toolbar is beneficial to some
users, it takes up display space that other users may want to use for
another purpose.
Required
Recommended
Dockable toolbars should remain open while a user is using them. The
user should be able to dismiss these toolbars when they are no longer
being used.
Optional
Recommended
Recommended
Make buttons and pixmaps in the toolbar the same width and height:
24x24 pixels for UNIX, JAVA, and HTML applications.
16x16 or 32x32 pixels for applications native to the Windows NT
operating system.
Chapter 5
139
Window Components
Toolbar Guidelines
Recommended
The graphics used in toolbar buttons should be chosen so that they are
not specific to any given culture.
Recommended
The graphics used in toolbar buttons should be provided in files that can
be replaced when localizing an application for a specific country.
Required
Required
If dockable toolbars are provided, break the toolbar buttons into sets of
similar types of functionality that users will want to use together. There
should be a separate dockable toolbar for each set of tools.
Recommended
Figure 5-5
Recommended
Limit toolbars to two levels of depth: a main level of tools, with the
possibility of lower-level tools in a cascading tool button. See Figure 5-5
for an example.
Recommended
140
Chapter 5
Window Components
Toolbar Guidelines
Recommended
The context list should control information presented in the scope pane,
results pane, and menu items in the menu bar.
Optional
Recommended
Required
141
Window Components
Toolbar Guidelines
placement rules that will help determine the views where toolbar items
will appear.
Required
142
Chapter 5
Window Components
Description Bar Guidelines
Recommended
Recommended
Recommended
Chapter 5
143
Window Components
Description Bar Guidelines
If the scope pane contains context tabs, the description bar should
indicate which context tab is active (such as Object Hierarchy or Task
Hierarchy).
If the scope pane does not have context tabs or a context list, the
description bar should indicate the contents of the scope pane. This
would be equivalent to the name that would be in the context list if
multiple contexts were available in the window.
Recommended
The portion of the description bar above the results pane should display
the name of the open object whose contents are presented in the results
pane.
144
Chapter 5
Window Components
Context Controls
Context Controls
Rather than opening new windows whenever the user wants to access a
different set of objects or a different type of functionality, HP OpenView
suggests the use of context controls. These controls allow users to change
between different management contexts within the application window.
Two different types of context controls can be found in HP OpenView
applications: a context list and context tabs.
The context list is presented as a combo box on the left side of the toolbar
in the window. This list presents the contexts that are available for the
user to choose.
Figure 5-7
Context tabs are tabs presented at the bottom of the scope pane. In
multiple-purpose presentation manager windows, the tabs can allow
users to change between objects, tools, tasks, management areas,
favorites, and help.
Figure 5-8
Context Tabs
Required
Chapter 5
145
Window Components
Context Controls
NOTE
Typically, context lists will be found in scope pane windows. Single pane
windows are less likely to have context lists.
Recommended
The context list determines the information presented in the scope pane,
results pane, any functionality provided through the menus and toolbar
buttons.
Recommended
Required
The name for a context in the context list should clearly indicate the type
of hierarchy or filter categories that will be presented in the scope pane.
Recommended
Recommended
Recommended
146
Chapter 5
Window Components
Scope Pane
Scope Pane
The scope pane is a vertical pane on the left side of the windows results
pane. Items presented in the scope pane provide users with the means of
navigating in the information space and controlling the information that
is presented in the results pane. Figure 5-9 and Figure 5-12 show
examples of scope panes.
General Guidelines
Recommended
Required
Required
If a user changes context with either the context list or context tabs, the
contents of the scope pane should change to match the new context
setting.
Recommended
Chapter 5
147
Window Components
Scope Pane
The Shift Tab keys should move keyboard focus to the context tabs (or,
if there are no context tabs, to the context list).
The Tab key should allow a user to navigate between the various
panes and controls in the window. The sequence of movement based
on the Tab key should be as follows:
1. Scope pane tabs
2. Scope pane
3. Results pane
4. Navigation tabs
5. Control pane
6. Context list
7. Scope pane tabs
If the window is split, Tab should move through the top half of the split,
followed by the bottom half, before moving to the context list.
For other guidelines on keyboard navigation in the scope pane, see
Keyboard Navigation in Tree List Controls in Chapter 9 .
148
Chapter 5
Window Components
Scope Pane
Figure 5-9
See also the guidelines in Interactions between the Scope Pane and
Results Pane later in this chapter.
Recommended
If multiple, unrelated sets of items (see the left figure in Figure 5-9) are
simultaneously presented in the same scope pane, all of the following
guidelines should be followed:
Each set should have a category heading (for example, System
Information).
Items within a set should be indented and listed under the headings
(for example, Disks, Printers, and Tape Drives).
Any selectable category headings should, when selected, cause the
results pane to display icons representing each item in the category.
As an alternative, category headings can be nonselectable.
Recommended
Chapter 5
149
Window Components
Scope Pane
For guidelines on navigation within a tree list and the behavior of the
controls within a tree list see Tree List Controls in Chapter 9 .
Recommended
The scope pane should present all container items in the hierarchy,
including a top-level item that is a container for all lower-level items.
Having a top-level item in the scope pane provides organization for the
user and allows him to access information on that items properties.
For example, in a hierarchy that shows the topology for the IP Internet,
the first item in the hierarchy should be IP Internet.
Optional
Both container and leaf-level items may be presented in the scope pane
unless the hierarchy will be large enough to cause performance
problems:
Examples of container items are task categories (such as
Configuration Tasks), information categories (such as System
Information), and compound objects (such as a network segment or a
computer system).
Examples of leaf-level items are individual tasks (such as Modify
SNMP Parameters), individual tools (such as CPU Utilization), and
lower-level objects (such as an IP Network Card).
Required
If leaf-level items (items that have no child items) are presented in the
scope pane for any portion of the hierarchy within a given context, they
must be presented for all portions of the hierarchy within that context.
Required
When the window is first opened the first container in the scope pane
should be expanded to show the user the items in that container.
It is confusing for users go into a window where the scope pane contains
a single entry that has not been expanded. Expanding the first container
in the hierarchy will provide greater visibility of available functionality.
It also provides sufficient visual cues to indicate that additional items
can be made available by expanding and contracting containers in the
scope pane.
Interactions between the Scope Pane and Results Pane
For further guidance, see Selection Guidelines in Chapter 7 .
150
Chapter 5
Window Components
Scope Pane
Required
When a scope pane window is first opened, the item in the scope pane
that corresponds to the information in the results pane should be
indicated as open.
An open item is visually indicated by a location cursor or a location
cursor plus a selection highlight surrounding it. See also Results Pane
below.
Required
When a container item is selected in the scope pane, the results pane
should display information that is relevant to the selected container.
Typically, the information presented is a view of the child items directly
under the container item.
For example, in a task presentation manager, the selection of the
container Service Tasks results in the presentation of a table with table
rows corresponding to the task folders and individual tasks contained
within Service Tasks.
In an object presentation manager, the selection of a container object
such as a network segment (for example, 10.5.106) results in the
presentation of the nodes within that segment (for example, the
computers, printers, bridges, and other network nodes).
Recommended
Required
Clicking on an expansion control in the scope pane must not change the
placement of the selection cursor nor the view presented in the results
pane.
Figure 5-10
Expansion Controls
Chapter 5
151
Window Components
Scope Pane
Required
Users should be able to scroll the contents of the scope pane without
affecting the information displayed in the results pane.
This allows users to easily move within the display space and to use drag
and drop between different views of objects.
Recommended
Required
Required
Required
Required
Double-clicking on the icon for a leaf-level object (that is one that does
not have a child view) in the results pane causes the default action
associated with that object to be executed or an error message to be given
to the user.
Typically the default action associated with an object is the presentation
of the properties of the object.
152
Chapter 5
Window Components
Scope Pane
Menus in a Scope Pane
There are typically pop-up menus associated with items in the scope
pane. See Pop-Up Menus in this chapter for guidelines related to these
pop-up menu items.
Visual Cues in a Scope Pane
Scope panes with hierarchical presentations of objects and tasks contain
a lot of visual cues that help guide the user in their interactions with the
application. Examples of the visual cues discussed in this section can be
seen in Figure 5-11.
Figure 5-11
Recommended
If the items in the scope pane are presented in a tree list, these items
should be represented by both a graphic and a label. The type of graphic
used should adhere to the following guidelines:
If the status of the represented object is normal, a 16x16 graphic that
depicts the object should be used.
For information on the design of graphical images see Symbol Design
Guidelines in Chapter 6 .
If the status of the represented object is abnormal, the object should
be represented by a symbol class shape that is colored to depict the
Chapter 5
153
Window Components
Scope Pane
abnormal status and the image for the object. The symbol class shape
should fit within a 20x20 square.
Abnormal status states in HP OpenView are critical, major, minor,
and warning. For more information on presentation of status
information see Use of Status Colors in Chapter 8 .
Required
Recommended
The position of the location cursor in the scope pane should be marked by
a location cursor or open indicator:
In applications native to the UNIX or Windows NT operating system,
the location cursor or open indicator should be the one by the
operating system.
In a JAVA applet or HTML application, the location cursor or open
indicator should be a black box that surrounds the name of the item
on which the location cursor is resting.
Recommended
The item in the scope pane that is currently open (the item whose
contents are displayed in the results pane) should adhere to all of the
following:
154
Chapter 5
Window Components
Scope Pane
It should be shown in the object_or_task_or_tool field of the title bar.
It should be shown by a label in a white navigation tab if navigation
tabs are provided in the interface.
It should be indicated by either:
A selection cursor, unless there has been a selection in the results
pane.
A location cursor, if there has been a selection in the selection
pane and the user has not navigated in the tree list with the
keyboard or keyboard- equivalent device.
Variations in the appearance of the icons to indicate the open object is
also allowed as a means of showing the open item. However, this type of
visual cue is not applicable to all types of icons (for example, servers,
services, computers, printers); therefore, it cannot be the only cue that is
provided for open.
Recommended
Items that have a symbol alert associated with them have an "!"
(exclamation point) to the left of the icons representing the object.
Chapter 5
155
Window Components
Scope Pane
Recommended
Recommended
If the scope pane presents filters, the material presented in the results
pane should be that information which matches the selected filters.
Recommended
Chapter 5
Window Components
Scope Pane
Recommended
A single-click on the check box for a filter should cause the selection of
the filter to be turned on or off depending on its previous state. It should
also cause the items which match that filter to be displayed in the results
pane.
Control of the information display by selection of categories should take
effect immediately without the need for the user to use a push button to
apply the filters. Compliance with this guideline may depend on
application performance.
Recommended
If the user must take a step to apply filters, there should be a [Display]
button associated with the scope pane that is continuously visible.
Chapter 5
157
Window Components
Results Pane
Results Pane
The results pane (or client area) is the area that is used for presenting
the primary information about managed objects and other application
functionality. Depending on the primary purpose of the application
window, the results pane will present different types of information.
Figure 5-13
Required
Recommended
Recommended
Recommended
158
Chapter 5
Window Components
Results Pane
Recommended
When a user first enters an applications window, the results pane should
not be empty. The results pane should show either:
Information relevant to the menu item, launcher entry, or selection
from which the user accessed the window (see Example 1 below).
Information that was visible when the user last exited the application
(see Example 2 below).
A default set of information. If the window is a scope pane window,
the default information should be associated with the first item in the
scope pane.
Example 1: If the user opened the window by double-clicking on an
alarm in an alarm browser, the window should present information
that is relevant to the alarm (for example, a view containing the
object that was the source of the alarm).
Example 2: If the user had previously had the window open and
showing the 12.1.5 subnet within the IP network hierarchy, the
window should open to that subnet.
Keyboard interaction in the results pane will need to vary depending on
the type of presentation format that is presented in the results pane. See
guidelines for keyboard navigation in see Presentation Formats for the
Results Pane."
Chapter 5
159
Window Components
Results Pane
Recommended
Recommended
Recommended
Recommended
160
Chapter 5
Window Components
Results Pane
Recommended
Chapter 5
161
Window Components
Results Pane
Recommended
Users should be able to use the arrow keys to navigate among the objects
presented in an iconic presentation format:
Pressing the up arrow should move to the nearest icon above the
current location.
Pressing the down arrow should move to the nearest icon below the
current location.
Pressing the left arrow should move to the nearest icon to the left of
the current location.
Pressing the right arrow should move to the nearest icon to the right
of the current location.
Recommended
162
Chapter 5
Window Components
Results Pane
Figure 5-15
Recommended
Chapter 5
163
Window Components
Results Pane
information on all of the objects within a view. Tables allow the display of
multiple pieces of information on multiple objects without cluttering the
display. Types of information that can be presented in a tabular format
are properties of the objects, important statistics, and multiple pieces of
static data.
When providing a tabular presentation format, refer to the guidelines in
this section and those on Tables and Grids in Chapter 9 .
Figure 5-16
Required
Recommended
Chapter 5
Window Components
Results Pane
which the object is being presented and use this as a basis for
determining what information should be presented. In a network
context, properties like IP address, subnet mask, and the number and
state of network cards or ports will typically be important to users. In
a system context, important properties could include the operating
system version, CPU usage, amount of RAM, available RAM, disks
mounted, and disk space.
Do not simply repeat the information that is provided in a existing
chart or graphical format.
While it is beneficial to repeat some information available in an iconic
view (for example, status and label), users do not go to a tabular view
to get a repetition of the information they had in another format.
Information like the symbol type and class should not be given in a
tabular view.
Present only a subset of the properties associated with an object.
If the table presents all of the properties associated with the objects
in a view, the table will become cluttered and will require too much
horizontal navigation by the user.
Recommendation
Recommended
The default sorting for a table in the tabular presentation format should
be alphabetical by object name or label.
Recommended
Chapter 5
165
Window Components
Results Pane
tabular view. Potential preferences that should be considered for user
manipulation include:
The properties to be presented.
The types of objects to be presented in the table.
The size of the columns in the table.
Which columns in the table are used to sort the information.
(Many table controls allow users to sort by clicking on the column
heading. This can aid users in finding information.)
Recommended
166
Chapter 5
Window Components
Results Pane
Figure 5-17
Recommended
Recommended
Chapter 5
167
Window Components
Results Pane
property inspectors and wizards. Property boxes, property inspectors,
and wizards typically present object properties in a secondary dialog box.
See Chapter 9 , Dialog Boxes and Controls. Form views are applicable
to both object and task presentation managers. Use the following
guidelines to determine when to use a property box, property inspector,
or wizard as compared to a form format in the results pane of a
presentation manager.
Figure 5-18
Required
Recommended
If a user has the results pane set to a presentation format other than the
form format and he requests the properties of an object via a menu or
toolbar button, these object properties should be presented in a
properties box instead of as a form in the main window area.
168
Chapter 5
Window Components
Results Pane
Recommended
Recommended
Recommended
Recommended
Chapter 5
169
Window Components
Navigation Tabs
Navigation Tabs
Navigation tabs are tabs that are presented at the bottom of the results
pane. Navigation tabs allow users the ability to quickly move back to a
previously accessed view in the results pane.
Figure 5-19
170
Chapter 5
Window Components
Navigation Tabs
In the stay on top state, the tab has a picture of the pin stuck
directly into the label, see Stay on Top Tab in Figure 5-20.
Figure 5-20
Required
If navigation tabs are provided, the tab that is currently on top or active
should appear in white, while any nonactive tabs appear in the same
color as the background for dialog boxes and scroll bars.
Recommended
When the user clicks on a navigation tab with the menu button on the
pointing device, a pop-up menu containing the following menu items
should be presented.
Reuse Tab
Keep Accessible This menu item causes the stick pin in the tab to be in
the pinned state (sideways pin). When the pin is in this
state, the tab for the view is maintained when the user
navigates to a new view. A new tab is created for
presenting the new view.
Keep Tab on Top This menu item is optional. When available, it causes
the pin on the tab to have a stuck in appearance. Until
the state of the tab is changed, it always remains on
top. This prevents the results pane from changing
when the user navigates in the scope pane.
Display in New Window This menu item causes the view associated
with the tab to be presented in a new window. If the
presentation manager supports child windows, the tab
is removed and a child window containing only the
identified view is presented. If the presentation
manager supports copied windows, a new duplicate
window is presented with view associated with the tab
set as the active view.
Chapter 5
171
Window Components
Navigation Tabs
Close Tab
Optional
When possible, have any menu items associated with the navigation tabs
available from the background pop-up menu for the view.
Recommended
Some of the menu items associated with the navigation tabs should be
presented as toolbar buttons in the toolbar:
Keep Accessible A toolbar button should be presented for changing the
pin state of the active tab between the Keep Accessible
and Reuse Tab states. This button should be a toggle
button.
Display in New Window This should be a regular toolbar button that
uses the graphic for display in new window.
Close
Optional
Recommended
If a tab is in the keep on top state, the selection of an item in the scope
pane should result in a nonactive tab (that is a tab that is overlaid by the
tab that is stuck) which contains the view associated with the selected
item.
172
Chapter 5
Window Components
Navigation Tabs
Recommended
Recommended
When a user moves the contents of a navigation tab into a child window,
the view associated with navigation tab that he most recently visited
should be presented as the active view in the parent window. Also, if the
tab is the last remaining navigation tab, the application should do one of
the following:
Present the user with a new tab and its associated view (for example,
last view visited, view located hierarchically above the current view).
Gray the menu item and toolbar button for Display in New Window
so that the user will not attempt to take this action.
Recommended
Recommended
Chapter 5
173
Window Components
Navigation Tabs
Present the user with a confirmation dialog to confirm whether
the user wants to exit the application.
Optional
Required
Recommended
Recommended
If the tab for the active view is not marked as keep accessible:
The tab should be overlaid when the user navigates to a new view by
selecting an item in the scope pane.
The tab should be released and should disappear when the user
navigates to a new view by selecting one of the keep accessible
navigation tabs.
Recommended
When there has been a change in status of the task or process that is
174
Chapter 5
Window Components
Navigation Tabs
going on in a view associated with a keep accessible navigation tab that
is not currently active, a visual cue should be presented on the left side of
the navigation tab. Recommended visual cues include:
A check mark to indicate that the user should check the view
contained on the tab (See Figure 5-21)
Recommended
The name presented in navigation tabs should be the name for the view
associated with the navigation tab.
For example, if the view associated with the tab is Segment 2, then the
tab should also contain the label Segment 2. Generic names should not
be used on tabs. See Figure 5-19 for an example.
Recommended
Recommended
Since the number of available tabs may be greater than the available
display space, a mechanism for scrolling navigation tabs should be
provided.
Required
All navigation tabs that have been marked as keep accessible must be
maintained regardless of context.
If there are multiple contexts in a presentation manager, users will want
to have quick access to views in different contexts. Users will not want to
change contexts to access the desired navigation tab. All navigation tabs
that have been marked as keep accessible should be added to the set of
available navigation tabs.
Required
Chapter 5
175
Window Components
Navigation Tabs
This is different from navigating by selecting items in the scope pane. If
the user navigates using the scope pane, the items that are selected in
the scope pane will clear any selections in the results pane and become
the new selection.
Required
Using navigation tabs to change views should cause the contents of the
scope pane to change to match the view associated with the navigation
tab.
When the user selects a navigation tab the object associated with view in
the navigation tab should be shown as the open object in the scope pane.
A location cursor, not the selection highlight, should be used to indicate
which object is open.
Required
176
Chapter 5
Window Components
Status Bar
Status Bar
The status bar is an optional area that should appear at the bottom of a
window. This bar provides users with state information about the
application when such information will help them perform their tasks.
Figure 5-22
A Status Bar
Recommended
Recommended
Recommended
If context sensitive active help is provided on menu items, the help text
should be displayed in the status bar.
Chapter 5
177
Window Components
Status Bar
178
Chapter 5
179
This chapter presents information on objects and the symbols that are
used to represent them. It also includes information on the symbols used
to represent actions in the toolbars and in executable symbols. The
chapter includes guidelines for the following areas:
When to represent objects with symbols in iconic views.
Hierarchies of objects presented in the scope pane.
Hierarchies of objects presented in the results pane.
Assigning symbols to represent objects, connections and actions.
Designing symbol classes for new types of objects and connections.
Designing symbol subclass graphics for new objects, connections and
actions.
180
Chapter 6
Iconic Views
An iconic view is a collection of symbols that are displayed in a single
results pane. An HP OpenView Network Node Manager (NNM) submap
is an example of an iconic view. Each view displays a perspective of the
objects and information being represented about the objects (for
example, internet, WAN, bus, service view). Sets of views are typically
organized in a hierarchical fashion.
Chapter 6
181
Required
Figure 6-1
Recommended
182
Chapter 6
Recommended
Recommended
Recommended
Example 6-1
Example:
Users are provided with a dialog box to choose the levels to be presented
in the hierarchy. The dialog box allows the user to choose the levels to be
combined and those to be eliminated.
Recommended
Applications should ensure that all object views that they create can be
accessed through the higher level views in the scope pane or through a
change in the setting of the context tab.
Although an application may not be interested in objects at all levels in
the hierarchy, it should create sufficient higher-level symbols to provide
users with appropriate contextual cues and navigation aids. In general,
it is not a good idea to present managed objects in views that do not have
a parent object or which do not allow navigation back to the root level for
the hierarchy.
Representation of Leaf-Level Objects
Leaf-level objects are objects that do not naturally contain other objects.
They may be associated with other objects and can have attributes.
Chapter 6
183
Required
Recommended
If the leaf-level object is selected in the scope pane, it should result in the
presentation of a form or table view that displays the attributes or
properties of that object. Menu and toolbar items associated with
accessing a iconic view should be grayed.
Iconic views that contain explodable symbols imply the ability to
navigate to a lower-level item. Users should not be presented with these
types of iconic views when they open an object that is a leaf-level object.
Recommended
Recommended
Example 6-2
Example:
An application for managing the configuration and maintenance of
Networked File Systems (NFS) is being developed. There is an existing
systems management hierarchy defined by another application that
supports application integration. For systems that have NFS configured,
two symbols are added in the computer view of the management
hierarchy. One symbol is for imported file systems and the other is for
exported file systems. When the user opens up the symbol for imported
file systems, they see individual icons representing each of the file
systems that have been imported.
184
Chapter 6
Example:
In the HP OpenView Event Correlation System (ECS) application, the
hierarchy of objects is based on the correlation that a user is creating to
do event correlation. The levels in the hierarchy are based on the
compound correlation elements that are developed as part of the
correlation. The contents at any level are based on the correlation
elements that the user has added in building the correlation.
Recommended
Example 6-4
Example:
In an application for managing processes, it does not make sense to
present processes inside an existing network hierarchy. As a result, the
application will need to develop a complete hierarchy for processes,
which would include the following: groupings of processes, individual
processes within the groupings, steps within each process, and actions
within steps.
Representing Objects Using a Combined Approach
Recommended
Chapter 6
185
Example:
An application that provides object discovery and status information for
an X.25 network could both integrate into an existing IP network
hierarchy of NNM and also provide users with a separate hierarchy that
only shows X.25 networking.
186
Chapter 6
IP Internet
X.25 Network
IP Internet
X.25
Node A
IP Internet
Node 3
IP Internet
Node B
IP Internet
Segment
Node 3
LAN
X.25
Segment
X.25
Node 1
Chapter 6
Node 2
Node 3
187
Chapter 6
Example:
User accounts defined by NIS are actually set up on the master NIS
server system. To simplify the management of individual systems, there
may need to be symbols for NIS users and UNIX users under each
system. The user login information for NIS is actually homed on the NIS
server, not on the individual client systems.
Users can do some management tasks when working with symbols for
objects outside of the objects home context. For other management tasks,
it will be better for users to quickly access the home location for these
objects.
Recommended
Objects that are presented out of their home context should be presented
with a symbol that indicates they are references or links to the actual
object. This symbol also indicates that the user can select the object and
view it within its home location. See Figure 6-3, later in this chapter.
Recommended
189
Objects that are not part of a given hierarchy, but which are related to a
given component in the hierarchy, should not be shown as part of the
hierarchy. Doing so can create recursion in the navigation. This recursion
can cause the user to get lost when trying to navigate to accomplish his
tasks.
Example 6-7
Example:
The following hierarchy has recursion:
domain->system->system components->users->tom->group
memberships->lab->members of lab-> tom
The recursion is based on the fact that tom is actually a leaf-level object
and his group membership is an attribute or property of tom, not an
object contained within tom. It would be best for the user if the object tom
were treated as a leaf- level object.
Recommended
Recommended
Recommended
The Go to Home menu item should work with related objects within
properties boxes that are presented in the results pane of the window. A
Go to Home push button for accessing the home hierarchy of related
objects should be provided in properties boxes presented outside of the
results pane. For more information see Representing Multiple Location
(Linked) Objects above.
190
Chapter 6
Figure 6-4
Chapter 6
191
Use independent views only for special-purpose capabilities that are not
intended to represent managed objects and their relationships.
Recommended
Choose a layout for the view which will match the users task needs given
the context and type of view.
Recommended
If the layout of the objects in the real world affects a users management
tasks, choose a layout algorithm and a sequencing of object symbols that
matches the real world.
Example 6-8
Example:
When creating a view which will display systems on a token ring, use the
ring layout. Sequence the systems in accordance with their sequence in
the token ring. If network elements are connected with a bus, the view
should have a bus layout.
Recommended
Example 6-9
Example:
A point-to-point layout would be used in displaying the flow of events
through different event correlation elements or in defining the flow of
steps in a process.
192
Chapter 6
Recommended
When using a tree layout for inheritance, objects with more general
information that is carried over to other objects should be presented at
the top of the tree. Objects which are more specific or which may
overwrite inherited data should be presented lower down in the tree.
Recommended
If a users task involves a logical ordering of objects and their real world
position is not important, choose a layout algorithm that will match the
way in which the user thinks about the objects.
A ring layout should be used when the connectivity between objects to
be represented is circular.
A star layout should be used only when a central object is in a
relationship with multiple peripheral objects.
Recommended
Recommended
Example 6-10
Example:
Systems running the Windows NT operating system are placed in row 1,
Windows 95 systems in row 2, HP-UX systems in row 3, and Solaris
systems in row 4. Within each row systems are alphabetically ordered
based on their hostnames.
Recommended
When a row/column layout is used, consider allowing the user the ability
Chapter 6
193
194
Chapter 6
Chapter 6
195
Choose symbol classes for objects that represent the type of object and its
role in the application view. See Table 6-2, Existing Symbol Class
Shapes, in the next section of this chapter.
Required
Choose the symbol class and subclass that best depict the role that an
object is playing given the context in which the symbol will be displayed.
Example 6-11
Example:
In a network hierarchy, a computer should be presented by a gateway
symbol if the computer is a gateway in the network that is being
displayed. But in a system management hierarchy, this same computer
would be better represented by the appropriate computer class symbol.
Recommended
Chose the symbol class and subclass for an object that will provide the
user with the most specific information available about the object.
Example 6-12
Example:
If the object is a computer and the application knows it is a PC with a
Windows NT operating system, use the symbol for the Windows NT
subclass, not the generic PC symbol.
Required
196
Chapter 6
Example:
Do not use the symbol for the TestMeasure: Analyzer to represent a
message-browsing capability that is presented via an executable symbol.
Required
Table 6-1
NetDevice:Analyzer
TestMeasure:Analyzer
NetDevice:Modem
Transceiver:Modem
NetDevice:PBX
Connector:PBX
NetDevice:X25
Connector:X25
Software: Mail
Application: Mail
Software: Database
Application: Database
Required
Chapter 6
197
Example 6-14
Examples:
If connection symbols are used to represent reporting relationships, a
dotted line is used to represent a loose reporting relationship and a
solid line for a more definitive reporting relationship.
Higher bandwidth connections would be represented by wide
connection symbols and lower bandwidth connections would be
represented by narrow connection symbols.
Recommended
Recommended
198
Chapter 6
Chapter 6
199
Symbol Classes
If new symbol classes need to be developed, they should not overlap with
the existing HP OpenView symbol classes. All symbol classes should be
mutually exclusive. The following section provides information on
existing symbol classes as well as guidelines for creating new symbol
classes.
Using Existing Symbol Classes
A variety of symbol classes have been developed for HP OpenView and
are shown in Table 6-2. If possible, choose from among these classes and
background class shapes when developing your application. Note that
Table 6-2 shows just the outside class shapes, even though the tables
descriptions also discuss the internal graphics that are appropriate for
each shape.
Recommended
200
Chapter 6
NOTE
Table 6-2
Symbol Class
Name
Class
Graphic
Symbol Class/
Subclass Description
Application
Cards
Client
Computer
Connector
Chapter 6
201
Symbol Class
Name
Class
Graphic
Symbol Class/
Subclass Description
Device
Domain
Location
Logo
Media
Network
202
Chapter 6
Symbol Class
Name
Class
Graphic
Symbol Class/
Subclass Description
Network Device
Server
Service
Software
Software Utilities
Chapter 6
203
Symbol Class
Name
Class
Graphic
Transceiver
Symbol Class/
Subclass Description
Intended for representation of objects that receive and/or
transmit information. The internal graphic indicates the
specific type of object (for example, a phone, modem,
satellite, or microwave station).
204
Chapter 6
New classes of icon symbols must have a unique outside shape that is
different from the outside shapes used in existing classes. A distinctive
outside shape is required for all new symbol classes. Refer back to Figure
6-2, X.25 Application Using a Combined Approach, for a list of outside
shapes being used by existing symbol classes.
The outside shape provides both a visual cue to a user of the class of
object that he is working with and a means of displaying status
information to him.
Recommended
Example 6-15
Example:
The client class is closely related to the server class. The two classes have
similar outside shapes. Members of the client class have a single inward
Chapter 6
205
Required
Required
Do not define a symbol class with a visual appearance that would include
existing members of other classes. Before a new connection symbol class
is defined, information should be obtained on existing, registered
connection symbol classes and subclasses; doing so will ensure that the
new symbol class being defined does not conflict with any
already-defined symbol classes and subclasses.
The overlay graphic is the visual cue to be used for identifying different
connection symbol classes. An example of an overlay graphic on top of a
connection symbol is shown below:
Recommended
Recommended
Overlay graphics must not have the potential for offending users.
Recommended
Recommended
Chapter 6
When an overlay graphic is defined via a color graphic, the colors used in
the graphic must minimize the use of color associated with overlay
graphics. Overlay graphics should consist of no more than two colors. It
is recommended that most overlay graphics be black and white.
Recommended
Example 6-16
Example:
Two connection lines have the same line style, but the overlay graphic is
different and this visual cue indicates to the user that they represent
different types of connection symbols.
207
Required
Table 6-4
Description
Adding items to a log file: for symbols that
represent the logging of different types of
information
208
Chapter 6
Description
Clipboard: for symbols that represent an
inventory of objects.
Chapter 6
209
Description
Envelope: for symbols that include the
concept of mail.
210
Chapter 6
Description
Line Graph: for symbols that represent
on-going data collection or presentation for
one or more variables.
Chapter 6
211
Description
Multitabbed folder: for symbols that include
the concept of a properties.
212
Chapter 6
Description
Question Mark: for symbols that include the
concept of help.
Chapter 6
213
Description
Trash can: for symbols that represent the
deletion or removal of something.
Recommended
Recommended
Required
New symbol subclasses must use the same outside shape as defined for
other symbols in that class. Do not create new symbols that belong in an
existing class of symbols and place them in a new symbol class.
214
Chapter 6
Required
Recommended
If a new graphic has concepts similar to other graphic that are already
defined for HP OpenView, the new graphic should use the same visual
cues as the existing symbols.
Recommended
Recommended
The graphics that are used for action symbols must provide a
representation of one or more of the following:
The type of functionality being provided by the control that the
symbol is associated with (such as using a curved arrow to represent
copying or installing).
The type of result that will be obtained as a result of the action (such
as installed software).
The type of object being acted upon (such as software).
Example 6-17
Example:
The symbol for a fax card contains the graphic for a fax device and the
class-specific graphic for a card.
Recommended
Example 6-18
Example:
A devil may be an easily recognizable symbol for a UNIX daemon, but it
should not be used as it has the potential to offend users. Graphics which
contain body parts (such as a hand) also may be viewed as offensive in
some cultures.
Recommended
Chapter 6
215
All graphics used for defining new symbol subclasses should come from
the network and system management domain or office domain; or they
should be logical or symbolic representations of the objects they
represent.
Recommended
Recommended
When the symbol subclass is defined via a color pixmap, the colors used
in the bitmap or icon should:
Come from the color palette provided by HP OpenView, see Chapter
C , Color Mapping and Palettes.
Use subtle. muted coloring in the pixmap image so that the image
does not interfere with the visibility of the status colors. This is
particularly important when users are interacting with a submap
crowded with numerous small images.
Provide the illusion of a concrete, three-dimensional object rather
than the effect of a lot of color in the image.
216
Chapter 6
Recommended
217
218
Chapter 6
Recommended
If there are multiple symbol classes that would be applicable for the
object within the active view, users should be able to chose between the
symbol classes in the Change Symbol Type dialog box.
See Figure 6-7 below for an example of a Change Symbol Type dialog
box.
Chapter 6
219
By default, users should be given the choice of adding symbols within the
symbol classes that are most appropriate for the active view. Symbols
that are not appropriate for the view should be excluded.
Recommended
220
Chapter 6
Recommended
Recommended
Chapter 6
221
222
Chapter 6
Example 6-19
Example:
If an application depends upon the notification of when new objects
are discovered and added to the NNM map, the application should
handle this notification when the submap containing the new object is
opened, as opposed to when NNM is first started.
If symbols are added to the child submaps, they should be added
gradually as submaps are opened, instead of when NNM is first
invoked. Note that a listing of submaps or objects in the map will
generally be incomplete, as the list will vary depending on which
submaps a user currently has open.
Recommended
Submap Context
The concept of submap context was developed to allow application
developers to tailor the menu items and toolbar buttons in each of their
applications submaps. Submap context better matches the menu items
and toolbar buttons in an application with the types of objects presented,
the type of management provided, and the user tasks performed.
Chapter 6
223
Required
Include context identifiers for the type of management that will be done
by the users of the submap (such as printer management, disk space
management, or IP network management).
Recommended
Optional
224
Chapter 6
Block generic menu items and toolbar buttons only if the submap is a
highly- specialized submap, where the inclusion of these items would
lead to user confusion and errors. Generic menu items and toolbar
buttons are blocked by specifying a submap context identifier of
NoGeneric. Examples of generic menu items are Print, Add Object.
Recommended
Block undefined menu items from submaps unless these submaps and
symbols are general ones that other applications are planning to build
upon. Pull-down menu items in applications that have not been
developed under the context-dependent paradigm will automatically
appear in submaps unless they are blocked. Contextually-undefined
pull-down menu items are blocked by specifying a submap context
identifier of NoUndefined.
Required
Recommended
Chapter 6
225
Required
Required
Example 6-20
Example:
An application could provide a menu item that would result in the tiling
of all submap windows open in the display if their geometry had not be
set by the end user.
Recommended
When specifying submap geometry, take into account all of the windows
that a user will simultaneously be using in his environment.
Before specifying submap geometry for any submap, develop an
understanding of what applications are likely to be in the users
environment and which ones he will use simultaneously. The geometry
for one applications submaps should not interfere with the use of other
applications.
Recommended
226
Chapter 6
The state of the overlay toggle should be left with the default of on if:
The submap is a regular submap window that is used to display the
topology of a set of managed objects. It is often difficult for
applications to identify at what level their customers will be trying to
do management. It is better to allow users to identify important
submaps that they do not want to overlay.
Users will want to go back and forth between different levels in a
Chapter 6
227
228
Chapter 6
229
230
Chapter 7
Selection Guidelines
Many HP OpenView applications use an object-action syntax in their
user interfaces. Users select symbols to indicate the objects that they
want to manipulate, then select menu items to initiate the desired
action. The selected objects make up the selection list.
Selection is a key aspect of user interaction with an application or set of
applications. Consistency in the way selections are made, how they are
displayed and how they are treated by the application is very important
for ease of learning of individual applications and transfer of training
across applications. Users do not want to learn special selection rules for
interacting with specific applications.
Chapter 7
231
Required
If the user makes an single selection in the scope pane or in the results
pane of a window, all other selections within the window must be cleared.
Required
When the user makes a single selection in the results pane, the selected
appearance of the open item in the scope pane must be removed and
replaced by a location cursor or an open indicator for the item in the
scope pane. See Figure 7-1 for an example.
Recommended
Required
If the user does a Ctrl+Select, the selection state of the item should toggle
to on if it was not previously selected or toggle to off if it was previously
selected and the selection state of other items within the window are
unchanged.
Required
Child windows and copies of application windows should have their own
selection lists that do not affect selections in the parent window.
NOTE
Child windows are windows which present a single view that was
originally presented in the presentation manager used for accessing
multiple views. Copies of the window refers to duplicate windows that
include all views within the parent window, not just a single view.
Recommended
When the user makes a copy of a window or moves a view into a child
window, the selections in the current and new window should be
unaffected.
232
Chapter 7
Users should be able to select items with the keyboard by pressing the
Space Bar or Enter key when the item has keyboard focus.
Recommended
Required
Required
Expanding and contacting items in the scope pane should have no affect
on the selection list.
Chapter 7
233
Users should be able to change the visible view without affecting the
selection list by:
Use of a navigation tab to access views marked as Keep Accessible
Use of a find or locate mechanism to open a new view in the window.
Required
Single clicking on an item in the scope pane to navigate, should clear all
existing selections, select the item the was clicked on and cause the
results pane to show a view associated with the item.
Required
234
Chapter 7
When the user does a single selection of an item in the scope pane to
navigate to a new view, this selection should clear the selections in the
results pane unless the user does a Ctrl+Select.
Required
Users must be able to use Ctrl+Select in the scope pane as well as the
results pane to toggle the selection state of the item under the pointer.
Required
Expanding and contacting items in the scope pane should have no affect
on the selection list.
Recommended
Required
When the user does multiple selection with Ctrl+Select, the selection list
must consist of all selected objects or items in the window, regardless of
whether they are visible or not.
Chapter 7
235
Required
236
Chapter 7
When the user does a single selection of an item in the scope pane to
navigate to a new view, this selection clears the selections in the results
pane unless the user does a Ctrl+ Select.
Required
NOTE
Ctrl+Select in the scope pane should not select the object that is only
being used for navigation. To have this object selected would require
users to take extra steps in order to obtain the selection list that they
would want to use. That is to remove the scope pane object from the
selection list, users would need to use Ctrl+Select to deselect the object.
Required
All of the selected objects in the window are listed in a user accessible
selection list. The selection list may be in a separate dialog box.
User testing has shown that users want to be able to see a list of their
selections when they are making multiple selections across different
views. Without this capability it becomes difficult for users to accurately
make their selections. .
When the user does multiple selection with Ctrl+Select, the selection list
must consist of all selected objects or items in the window, regardless of
whether they are visible or not.
Required
Chapter 7
237
If the user selects an item at a higher level in the hierarchy, all items
contained within the higher level item should be marked as selected (for
example, black check mark in the associated check boxes).
Required
When the user has selected a subset of items beneath a higher level item,
the check mark in the check box of the higher level item should be light
gray instead of black to indicate that the item is partially selected.
The selection of a subset of items can be accomplished by directly
selecting some of the lower level items or by deselecting a subset of lower
level items that under a previously selected higher level item.
In Figure 7-2 below, the left most graphic shows what the tree would look
like with no selections. If the user directly selected HP-UX, the higher
level item Nodes would be shown as partially selected, see the graphic
in the middle. As is shown in the right most graphic, if the user directly
selected Denver the lower level items under Denver would
238
Chapter 7
Recommended
Required
Clicking on the check box or on the icon to make the item part of a
multiple selection should not affect the position of the selection cursor or
location cursor if the tree list is presented in the scope pane.
Group Selection for Container Symbols
In the OpenView management environment there are many container
symbols that are of interest to the user as an object and which contain
other objects. For example, a network is a container for computers,
connectors, and network devices but it also can be viewed as a object for
which the user wants to obtain and monitor data. A computer is a
container for software, interface cards, etc., and it is also a specific device
that users want to manipulate.
To allow flexibility to accommodate user needs, containers should allow
users to easily:
Select the container object without selecting the objects contained
within.
Select all of the objects contained within the container.
Chapter 7
239
Recommended
A pop-up menu item should be provided for selecting of all of the objects
contained within the container symbol. The menu item should be labeled
Select Grouped Items
Recommended
When objects are selected by selecting the container, the selection list
should either list all lower level items that have been selected or provide
a visual cue associated with container item so that it can be
distinguished from items that were not selected via a group selection.
Recommended
When objects are selected with a group selection, menu items executed
on the group should act on the subset of items in the group to which they
are applicable. Menu item graying should be disabled when a group
selection is in effect.
Recommended
Recommended
240
Chapter 7
If the application or tool is implemented using the OVw API and it uses
the HP OpenView Windows selection list, provide users with a
mechanism for accessing the HP OpenView Windows selection list once
your application is started.
The application involves the manipulation of different sets of objects
used in different capacities.
For example, in a software distribution tool that requires the user to
identify a list of nodes that will receive software and the server that
will be used for the update, the user could use the HP OpenView
Windows selection list to specify the target nodes before the
application is launched. Once the tool is running, the user could use
the HP OpenView Windows selection list to select the server node.
Successful completion of the users task requires re-running the
application with a different set of selected objects.
For example, a diagnostic tool indicates that there is a configuration
discrepancy between a selected node and one or more nodes that were
not previously in the tools selection list. To isolate and fix the
problem the new nodes must be in the selection list.
After running the application with one set of objects, the user wants
to re-run the application with a new set of objects.
Chapter 7
241
Applications other than NNM should only modify the Open View
Windows selection list based on an explicit user request through a menu
item or a push button.
Required
Chapter 7
Chapter 7
243
The visual cue for a copy operation is a + sign associated with the pointer
when the object is being dragged over a drop target that would result in a
copy.
Recommended
The visual cue for a move operation is the pointer when the object is
being dragged over a drop target that would result in a move.
244
Chapter 7
When an object is being dragged over a drop target that will not allow a
drop, it is recommended that the user be presented with a not sign in
association with the pointer.
Recommended
The application should create any new symbols or table entries required
at the drop target as a result of the drag and drop operation.
Chapter 7
245
Recommended
If the drop target is a graphical view and automatic layout is off, the
dropped symbol should remain at the location where the user dropped it.
Recommended
If the drop target is a graphical view and automatic layout is on, the
dropped symbol should remain at dropped location for 3-5 seconds and
then be moved to a position that is consistent with the layout algorithm
and which is as close as possible to the location where the user dropped
the symbol.
The automatic layout algorithm should never cause the symbol to be
moved to a location that is not visible in the current viewing area of the
window. If the automatic layout algorithm would cause the symbol to
move to a location that would be out of the visible display space, the
window should be automatically scrolled so the dropped object is visible.
Recommended
If the drop target is a tabular view, the dropped entry should remain at
the location where the user dropped it. The entry should be
automatically selected to aid the user in identifying it.
Recommended
If the user takes an action to sorting the information in the table, the
dropped entry should be placed in a sequence based the sorting
algorithm specified by the user. The entry was selected, it should remain
selected to aid the user in identifying it.
Recommended
If the dragged object is a table entry and the drop target has different
table entries than the view that was the source of the drag operation, the
table entry for the dropped object should automatically be modified to fit
the table in which the object was dropped or the drop target should reject
the dropped entry. If the name field is the only field that is applicable for
the dropped object, all other columns in the table should be blank or have
a dash in them.
Recommended
If the user drops an executable symbol into a view, the executable symbol
should be placed in the view if it has the characteristics that are required
for that view. The action associated with the executable symbol should
not be executed.
Recommended
If the dropped symbol or table entry does not have the characteristics
that are required for the view:
246
Chapter 7
Recommended
Recommended
Recommended
Recommended
Chapter 7
247
If the dropped symbol or table entry does not match the characteristics
that are required for the any of the views under the compound symbol:
The drop operation should result in a presentation edit where the
dropped object(s) is presented in the user plane for the child view
under the symbol.
or
The drop operation should be rejected and the symbol or table entry
should be bounced back to its original location.
Leaf Level Symbols as Drop Targets
Leaf level symbols are typically presented in the presented in views in
the results pane. Leaf level symbols may also be presented in the scope
pane.
When a dragged item is dropped on to a leaf symbol, the dropped object
cannot appear in a child view. By definition, leaf level symbols are ones
that do not contain other objects. However leaf level symbols do have
attributes or properties with which the dropped object can be integrated.
Recommended
If the user drops a object symbol, group symbol or table entry on to a leaf
level symbol, the drag operation should result in a change in the
attributes associated with the leaf level symbol or the drop operation
should be rejected.
Recommended
Recommended
Recommended
If the user uses the pop-up menu to select all items in a container and
248
Chapter 7
Recommended
Recommended
If the data change is not obvious given the type of dragged item, or the
drop target behavior is severe or unrecoverable, the application must
provide a warning dialog (after the drop) which permits the user to
cancel the action.
Chapter 7
249
Drop target help should be provided for all application registered drop
targets that have behavior that is different than the default.
Recommended
Recommended
250
Chapter 7
Visual Presentation
251
Visual Presentation
This chapter presents design and style guidelines for the use of visual
presentation capabilities, including:
Status and events
Highlighting symbols
Symbol alerts
Text annotation
Flashing symbols
Transparent symbols
Executable symbol appearance
Partially filled connection symbols
252
Chapter 8
Visual Presentation
General Guidelines
General Guidelines
Overuse of visual cues in applications will result in visual clutter and
will interfere with the effectiveness of these visual cues.
Recommended
Chapter 8
253
Visual Presentation
Notification of Object Conditions
Recommended
254
Chapter 8
Visual Presentation
Notification of Object Conditions
Status color should be used as the primary visual cue for summarizing
the operational or administrative status of a managed object presented
in an iconic view.
Recommended
Required
Status color must not be used to notify users of a specific condition (for
example, system rebooting) or to indicate what type of action a user
should take with regard to the state of an object. This detailed
information should be provided through other mechanisms (events,
symbol alerts, text annotation, and others).
Required
Users should be able to configure the colors used for status color.
Approximately 7% of the users are likely to be color blind. The ability to
configure the colors used for status will allow color impaired users to
choose colors that they can differentiate in terms of brightness when
they are unable to differentiate the hues.
Required
The default status colors used by applications must match the default
status colors defined for HP OpenView.
Table 8-1
Color
RGB Value
Status Type
Critical
Red
Operational
Major
Orange
Operational
Minor
Yellow
Operational
Warning
Cyan
Operational
Chapter 8
255
Visual Presentation
Notification of Object Conditions
Table 8-1
Color
RGB Value
Status Type
Normal
Green
Operational
Unknown
Blue
Operational
Unmanaged
Off White
Administrative
Disabled
Brown
Administrative
Testing
Tan
Administrative
Restricted
Light Pink
Administrative
The status coloring of objects that contain other objects should be based
on the status of all contained objects that are relevant to the current
context.
Example 8-1
Example
In a context for file server management, the status of the server should
be based the servers file systems, network card, processes related to
serving the file systems and connecting to the network. The status of the
printers on this system and processes related to these printers should
not contribute to the file servers status coloring.
Recommended
The status coloring of leaf-level objects that do not contain other objects
should be based on the status of object attributes that are relevant to the
current context.
256
Chapter 8
Visual Presentation
Notification of Object Conditions
Example 8-2
Example
In a context for file server management, the status of the network card
should be based on whether the network card is functional and
connecting the server to the network.
Status Source in NNM
HP OpenView Network Node Manager (NNM) provides a choice status
sources for the setting status of status colors by applications. The status
source choices are by object, by symbol, or by compound status. The
following guidelines should be used by applications integrating into
NNM.
A single real world object can be acted on and monitored by multiple
status setting applications. Users may need and want to have status
information from all of the different applications.
It is undesirable to have more than one application setting status on a
single symbol since it can result in applications changing the status color
back and forth as their polling alternates.
To avoid this conflict, follow these guidelines.
Recommended
Only the owner of a symbol should set its status source. The owner of a
symbol is determined as follows:
An application that creates a symbol is its owner.
For a user-added symbol, the first application that accepts the symbol
into the application plane is its owner. The application that created
the submap to which the symbol is added is given preference over
other applications if it accepts the symbol into the application plane
at the time the symbol is added.
The application designated as the owner of a symbol appears first in
the list of interested applications found in the symbol information
structure for that symbol.
Recommended
Recommended
Object status source should only be used by the application that created
the object in the HP OpenView Windows database (ovwdb).
Chapter 8
257
Visual Presentation
Notification of Object Conditions
Recommended
Recommended
258
Chapter 8
Visual Presentation
Symbol Alerts
Symbol Alerts
Support for symbol alerts is only provided for applications integrating
into NNM on HP-UX and Solaris. All applications may use symbol alters
but may need to implement them on their own.
Symbol alerts are dynamically displayed graphics that are linked to
symbols used to represent objects or connections. They are used to notify
users of alarms, critical events, or of changes in status where a single
symbol may have multiple attributes for which status is set. Symbol
alerts may be presented in the scope pane of a window or the in the
results pane. Symbol alerts in the results pane are not scaled and cannot
be occluded by object symbols, therefore, they provide a very powerful
visual cue to the user.
Figure 8-1
Figure 8-2
Chapter 8
259
Visual Presentation
Symbol Alerts
If symbol alerts are used, their primary purpose should be to notify the
user of an important event or condition that requires user attention and
to allow the user to take quick action on the condition that led to it.
Required
Required
Recommended
To allow symbol alerts to better meet user needs, the application should
allow HP OpenView administrators to choose the level within the
hierarchy at which the symbol alerts will be presented.
260
Chapter 8
Visual Presentation
Symbol Alerts
Recommended
Recommended
Create new symbol alert graphics for notification only if the event or
condition is of a very special type and requires the user to recognize it as
different from the other notifications that they will encounter. See the
The Integration Series: HP OpenView Windows Developers Guide for
information on creating new symbol alert types.
Recommended
If there are multiple different alarms associated with a single object that
would result in a symbol alert, adhere to all of the following guidelines:
Display only a single symbol alert in conjunction with the symbol for
the object. The multiple alarms should all be associated with this one
symbol alert.
Display the symbol alert with a severity that corresponds to the most
severe alarm condition.
Example 8-3
Example:
If there are two alarms associated with a given symbol alert, one with
minor severity and one which is critical, the symbol alert should be
red to show the critical severity.
Use the pop-up menu associated with the symbol alert to provide the
users with a means of viewing all of the alarm conditions that led to
the symbol alert.
Recommended
While the symbol alert is visible and has not been deleted, users can be
notified about duplicate alarms by presenting a number to indicate the
number of messages of the same type.
Required
Once the condition associated with the symbol alert has been resolved,
the symbol alert must be removed, whether or not the user has
responded to the alert.
Required
Chapter 8
261
Visual Presentation
Symbol Alerts
Execute an action that will allow the user to immediately respond to
the source of the alert.
Result in the presentation of a view of the object whose condition
resulted in the symbol alert. This view should allow the user to take
direct action to fix the problem.
Example 8-4
Example:
A symbol alert on a location icon opens a submap for the card drawer
on a switch. At this level users can identify the card with the problem
and use the menu items to take action.
Recommended
Recommended
The pop-up menu associated with symbol alerts should adhere to all of
the following guidelines:
The default action that would be executed by double clicking on the
symbol alert should be the first item in the pop-up menu.
The pop-up menu should provide access to a textual message
describing the condition that led to the alert.
The menu should provide access to actions that the user can take to
fix the condition that led to the alert.
The menu should provide access to views of the object whose
condition led to the symbol alert.
If there are multiple alarms associated with the symbol alert, the
menu should provide access to information on what the various
alarms are and should allow the user to chose the sequence of trying
to handle these problems.
The menu should allow acknowledgment of the symbol alert.
Acknowledgment of the symbol alert should cause the symbol alert to
be deleted and should prevent the display of additional symbol alerts
resulting from the same or duplicate alarm conditions, whether or not
the problem was fixed by the user.
262
Chapter 8
Visual Presentation
Symbol Alerts
Figure 8-3
Chapter 8
263
Visual Presentation
Text Annotation for Symbols
Required
Recommended
264
Chapter 8
Visual Presentation
Highlighting Symbols
Highlighting Symbols
One of the visual cues defined for HP OpenView is the highlighting of
symbols. Highlighting of an object symbol results in the inverse video
appearance of the symbol label. Symbol labels generally include black
text on a white background. The label of a highlighted object symbol
appears as white text on a black background. Highlighting of a
connection symbol is presented as the overlaying of the symbol with a
distinctive color.
It is recommended that highlighting be used for the following purposes:
Recommended
Recommended
Recommended
Optional
Required
Recommended
Required
Chapter 8
265
Visual Presentation
Flashing Symbols
Flashing Symbols
Developers to cause symbols to flash, and to turn off this flashing. If
flashing symbols are used in the application adhere to the following
guidelines:
Required
Flashing should be used only for high severity conditions where users
must handle the condition immediately; generally this is when the
symbol has a status of major or critical.
While useful for attracting the users attention, flashing can be annoying
and stress producing. If over used, this visual cue can interfere with user
performance.
Required
If flashing symbols are used in the application, users must have a means
of configuring the application so that flashing is turned off.
Required
Flashing must never be the only visual cue used to notify a user of a high
severity condition.
If flashing is turned off, your application must have another mechanism
for notifying users of the high severity condition; for example, status
color, symbol alerts, or text annotation.
Recommended
266
Chapter 8
Visual Presentation
Transparent Symbols
Transparent Symbols
When assigning symbols to objects, you can choose to present the
symbols with a class background shape or as transparent symbols that
do not have a class background shape. Transparent symbols do not
display their background shape and status color as long as the object
associated with the symbol has normal status. While in normal status,
only the inside graphic is visible in transparent symbols.
For applications integrated into NNM, end users can override a
developers setting for symbol transparency.
Use the following guidelines in determining if objects should be
presented with transparent symbols or regular symbols.
Recommended
Required
Chapter 8
267
Visual Presentation
Transparent Symbols
The mixture of different types of symbols in the same view will be
confusing to users.
If the view containing the object symbol will be resized to a point
where the graphic will no longer be visible.
The change from a graphic without a background shape to one with a
background shape with no graphic will be confusing to users.
If users will need to differentiate between the different classes of
objects to accomplish their management tasks.
The class of the object is visually represented by the background
shape. When transparent symbols are used the visual cue for the
object class is not available.
If users will want to use drag and drop and the transparent symbols
are presented through HP OpenView Windows.
In HP OpenView Windows, the hot spot for the symbol is defined to
include the space that would be occupied by the class shape. Symbols
for objects can partially overlap. When the symbols are transparent,
it is impossible for users to determine which symbol is on top. This
lack of visible symbol boundaries may cause users to make errors
when dragging and dropping.
268
Chapter 8
Visual Presentation
Executable Symbol Appearance
Required
If executable symbols are used, the symbols should be presented with the
default executable symbol appearance (that is, box around symbol) if any
of the following are true:
The executable symbol is being used to provide quick access to
application functionality (such as the presentation of an application
tool, graphed data, etc.).
The intent is for users to execute actions on objects by dragging and
dropping other symbols on to the executable symbol.
Recommended
Required
Chapter 8
269
Visual Presentation
Executable Symbol Appearance
Objects dropped on to the symbol during a drag and drop operation
must be acted on as if they were the selection list for the executable
action.
Required
270
Chapter 8
Visual Presentation
Partially Filled Connection Symbols
271
Visual Presentation
Partially Filled Connection Symbols
When defining percentage fill for the connection symbol:
Required
Required
The area displayed in the secondary status color should represent the
amount of the capacity that is available for use.
Recommended
When the line is down, the percent fill should be 100% to indicate that
none of the capacity is available for use. The status color for the
connection should be consistent with the state (for example, critical).
Recommended
The primary status color for a connection symbol should indicate the
quality of the connection (for example, how much noise is on the line,
how much data is being lost, if the connection is down).
Optional
Recommended
Recommended
Recommended
Consider providing a menu item that will display a numeric value for the
used and/or available capacity for a connection. The results of this item
could be presented in a dialog box or as text annotation on the
connections themselves.
272
Chapter 8
273
274
Chapter 9
Title Bar
The content of the title for dialog boxes will vary depending on the
purpose of the dialog box.
Recommended
The title of dialog boxes should adhere to the conventions in Table 9-1.
As in the title bar for windows, the application name in the title bar
should be presented in abbreviated form. Include the <objectname> only
if there is only one object. Include the <toolname> only if there are
multiple tools associated with an application. The <actionname> should
be associated with the menu item that led to the dialog box.
Table 9-1
Usage
Format
Message
<objectname> - <appname>:<toolname>
Progress
<objectname> - <appname>:<toolname> or
<actionname>
Action (Command)
<objectname> - <appname>:<actionname>
Object Properties
<object> Properties
Application Options
<appname>:<toolname>-<type> Properties
Focus
The initial focus of a dialog box should be based on what actions are
required of the user. Provide visual cues to guide users in their tasks; for
example, use the location cursor or the text cursor.
Chapter 9
275
The location cursor should be in the first field the user is likely to modify.
Required
If the location cursor is in a text field, the text cursor should be placed at
the most likely point of modification; the beginning of an empty field and
the end of a field already containing text.
Recommended
Text cursors should not appear in every modifiable text field. Only one
text cursor should be visible at a time.
Recommended
Use cursors to indicate the field that has keyboard focus, and provide
visual cues to guide users in their tasks.If the choices available in a given
field are dependent on the value assigned to a prerequisite field, then do
one of the following:
Place the prerequisite field above dependent fields to encourage users
to input data in the prerequisite fields first.
Display only the prerequisite field and wait until the user assigns a
value to it before displaying the fields or options that are dependent
on that value.
Menu Bars
Recommended
Whenever possible, use the font size chosen by users in their system level
font specifications (that is, VUE, Windows NT operating system).
Recommended
When using a different font size than that set by the users environment,
consider the effect of display size and resolution on the readability of the
fonts. As display resolution increases (for example, 800 x 600 to 1280 x
276
Chapter 9
Test the default size of the largest application windows on the smallest
monitor with the lowest resolution that is anticipated to be used by
customers (for example, 13 inch 800 x 600 monitor). Make sure that the
whole window and all of its controls fit easily into the display. Make sure
to test the application using a font size that will also be readable on the
highest resolution monitor used by customers (for example, 1280 x 1024
monitor).
Required
Test the default size of the smallest application controls on the smallest
monitor with the highest resolution that is anticipated to be used by
customers (for example, 13 inch 1280 x 1024 monitor). Make sure that
there is adequate distance between controls and that all controls can be
easily activated without error.
Chapter 9
277
The following user goals should guide the resize behavior for the dialog
boxes and windows that are resizable by users.
View more information by enlarging the window.
View information in a larger size (that is, for scaled views of objects).
Create more room on the desktop by shrinking the window.
When operating in accord with this goal, users will want to see the
most important information in the window or dialog box, otherwise
they would iconify the window.
Panes in Resized Windows
When a user enlarges or shrinks a window or dialog box that has
multiple visible panes, they typically do not want to resize only one pane.
They would like the resize operation to affect all panes. Users also want
to make choices between which pane will get the most space.
Recommended
Recommended
Controls for resizing window panes should be provided when users will
benefit from differential sizing of the panes.
User Help
Recommended
Provide help text for every dialog box. Help can be accessible from a
[Help] button in the right corner of the button box at the bottom of the
dialog box, from the F1 key for context sensitive help, or from a question
mark in the title bar of the dialog box for whats this help.
278
Chapter 9
NOTE
Chapter 9
279
Recommended
If labels for controls are related to database fields, both labels should be
meaningfully stated in terms and relationships that the user is likely to
understand.
Recommended
Recommended
Recommended
For option buttons (UNIX only), place a colon (:) after the label if it
precedes the option button.
Visual Cues in Labels
Provide visual cues to indicate the state and type of action of controls.
Required
280
Chapter 9
Place an ellipsis (...) after the label on buttons that lead to a dialog box to
which the user must respond before an action can take place.
NOTE
Required
Do not place any symbols after the label on buttons that lead to an
immediate action (sometimes known as command buttons).
Recommended
Provide a clear indication of which fields in the dialog box require user
input (mandatory fields) and the fields for which user input is optional
(optional fields). Either:
Place parentheses around the label for controls in optional fields;
For example: The label for the text fields in which users may enter
comments should be (Comments:).
Label the fields with mandatory and optional.
Required
Place two arrows ( >> ) after the label on the button that leads to the
expansion of a window to display a previously invisible pane. The arrows
should indicate the direction of the expansion of the window.
To aid the user in understanding the functionality of the button, it is
good to provide a textual label, such as More>>.
General Guidelines
Complexity in dialog boxes should be appropriate for the task
Recommended
Chapter 9
281
Recommended
Recommended
Default Values
Default values are the values that are set by the application so that they
appear as the initial settings for controls when users access them for the
first time. Default values reduce task time by minimizing the number of
fields the user needs to complete, and by providing examples of valid
entries that users can modify. Providing good default values will
minimize the need for users to do extensive customizing prior to use of
the application. Users should not be required to provide any information
that the application can supply for itself.
Recommended
Provide default values for each control in the dialog box unless a default
would lead to destructive consequences or to user errors.
Recommended
Default values should be chosen to support the users task, all of the
following guidelines should be adhered to when choosing the default
values:
282
Chapter 9
Recommended
NOTE
Recommended
If it is not likely that users will want to retain their previously set
values, application specified defaults or customized defaults should be
Chapter 9
283
NOTE
The default values that are used for fields in the dialog box or form can
be a combination of previous user values, user configured values and
system default values. For example, in a print dialog box, the default
printer could be set to the last printer selected by the user, however, the
format of the printout could be that defined by the application for the
report that is being printed.
Recommended
If there is a default for a control or field in a dialog box, the default value
should be visible when the field is first presented or as soon as sufficient
information is available for the application to set the default value.
Recommended
Default values for text boxes and combination boxes should be editable
by the user using conventional editing commands.
Default Actions
Default actions result from the user pressing the Return or Enter key, or
by double-clicking on an item, symbol, or control. Following are general
284
Chapter 9
Recommended
In simple dialog boxes with no input fields or only one input field, both of
the following guidelines should be followed:
One of the push buttons, [OK], [Cancel], or [Close], should be
defined as the default action when the user first enters the dialog box.
The the choice of default action should be based on which action
would be the safest for the user.
Recommended
Chapter 9
285
286
Chapter 9
Push Buttons
Recommended
Chapter 9
287
Push Buttons
Required
Limit the use of push buttons in presentation managers and the primary
application window. Provide access to commands or operations through
the toolbar, through pull down or pop-up menus, or by executable
symbols.
Placement
Follow the general guidelines for the placement of controls presented in
this chapter under General Guidelines for Controls in Dialog Boxes.
Also follow the specific guidelines for push buttons presented in this
section.
NOTE
Push buttons may be placed at the bottom of the dialog box or in the
main portion of the dialog box.
Required
Recommended
Required
Required
Place push buttons applicable to a list to the right of the list to which
they apply. Vertically align the left side of each push button.
288
Chapter 9
Sequence push buttons that select and act on items in a list at the top of
the set of buttons, for example [Open]. Place buttons that modify and/or
delete items in a selection list at the bottom of the set of buttons.
Recommended
Push buttons placed at the bottom of the dialog box should be aligned
starting at the right side of the window.
Recommended
The distance from the window or dialog box border to the edge of the
button should be a minimum of 7 dialog base units, or 7 to 11 pixels wide.
Recommended
Recommended
Recommended
Required
Table 9-2 outlines the labels and definitions that are required for push
buttons in HP OpenView applications.
Chapter 9
289
NOTE
Do not label buttons at the bottom of the dialog box or window with the
word [Exit]. [Exit] should be reserved for exiting the HP OpenView
application or HP OpenView environment as a whole. Cognitively, users
view the completion of a dialog box as simply closing the window in
which the dialog box is presented.
Table 9-2
Key
Action
[Yes]
Applies an affirmative response to the question in the dialog box and closes the
dialog box.
[No]
Applies a negative response to the question in the dialog box and closes the dialog
box.
[OK]
Validates the user-specified action in the dialog box, and closes the dialog box. If
appropriate, saves changes in the dialog box.
[Apply]
Applies operation of the dialog box with the current settings. This includes any
changes in the dialog box. The [Apply] button should be grayed when the dialog
box is first accessed. It should be made available as soon as the user makes any
change in the dialog box.
[Reset]
Cancels any user changes that have not been applied. Also resets the status of the
dialog box to its initial state. Users can undo changes by doing a [Reset]. [Reset]
does not close the dialog box. The [Reset] button should be grayed when the
dialog box is first accessed.
[Cancel]
Cancels the changes in the dialog box without performing any actions that has not
been previously applied. [Cancel] closes the dialog box. The [Cancel] button
should be available when the user first accesses the dialog box.
[Close]
Closes the dialog box without performing any actions in the box. If the dialog box
does not allow for user input and changes, it should contain a [Close] button
instead of [Ok] and [Cancel] buttons.
[Help]
Provides help for the dialog box. This button should always be available.
[Select]
[Add]
Adds a new item to the list of items. This button should be grayed when its text input
field or list of selections is empty.
290
Chapter 9
Key
Action
[Delete]
Deletes the items from the list. In some cases this will result in a deletion from the
application. This button should be grayed when its list of selections is empty.
[Describe] or
[Describe/
Modify]
[Modify...]
Presents a dialog box for modifying an item chosen in a list box. May be combined
with Describe as in [Describe/Modify].
[Properties]
Presents a dialog box that indicates the properties of an object or application and
allows the user to change modifiable fields.
Visual Cues
Required
Provide visual cues for the availability of push buttons. If a button is not
currently available for use, gray the label for the button. If a button is
never available for use, it should not be presented in the dialog box.
Examples of when specific push buttons should be grayed are presented
in Table 9-3.
Table 9-3
Button
[Reset]
No changes have been made in the dialog box since the last use of [Apply].
[Next]
[Previous]
[Apply]
No changes have been made in the dialog box since the last use of [Apply].
[Cancel]
No changes have been made since the last use of [Apply]. [Cancel] should not be
grayed when the user first accesses the dialog box.
Default Action
Follow these guidelines and the guidelines in Default Actions on page
284 when assigning default actions to push buttons.
Chapter 9
291
Required
If the location cursor is in a single line text field and there is a push
button associated with the text field, the default action should be to
activate the push button, and the location cursor should remain in the
text field.
Required
Figure 9-2
Recommended
Option Buttons
An option button produces an option menu from which the user can
choose a single item. Option buttons are available only in UNIX. For
applications on Windows NT, use combination boxes.
Figure 9-3
Recommended
292
Chapter 9
NOTE
If some, but not all, valid options are known, use a combination box in
place of an option button.
NOTE
The recommendation for the placement of the option button and its
labels may need to be modified for localization for different countries.
Recommended
If the content of the option menu is not appropriate given the current
state in the window or dialog box, the labels both inside the button and
next to the button should be grayed.
Recommended
Place the label that defines the use of the button to the left of the button
to which it applies, as shown in Figure 9-3. The label for the value set for
the control should be shown on the button itself.
Chapter 9
293
If the location cursor is on a menu item within the option button, the
default action should be to accept the menu item as the value for the
control and move the location cursor to the next control.
Recommended
The default value for an option button should be the choice most likely to
be selected by users.
Radio Buttons
Radio buttons can be used in dialog boxes, panes of windows, or in
menus. Radio buttons occur as a set and allow for the selection of a single
alternative within the set. Radio buttons are sometimes referred to as
option or toggle buttons.
Figure 9-4
Radio Buttons
Recommended
294
Chapter 9
NOTE
Required
Label the header for a set of radio buttons to indicate the variable that is
being modified by the buttons.
Recommended
Place the header for the set of radio buttons above the radio buttons.
Required
Label each button to indicate the value or state that will be active when
the given button is set to On.
Recommended
Place the state indicator button to the left of the button label.
Recommended
Optional
Required
295
The default value for a set of radio buttons should be the choice most
likely to be selected by users.
Check Box
A check box is a toggle control in which the user makes the logical choice
between A and Not A. In groups of check boxes, each check box
represents an independent choice. However, check boxes are most
obvious in their meaning when they occur in groups of two or more.
Recommended
The use of a check box is recommended when most or all of the following
conditions are met:
The desired result is the making of a choice or the setting of a state.
Each setting is a single choice between two states.
Choices can be meaningfully portrayed as an on-off state.
Users need to quickly see the current state of the choices.
Users will clearly understand the meaning of the choice when it is
selected or not selected.
Placement and Labeling
Follow the general guidelines for the placement and labeling of controls
presented in this chapter under General Guidelines for Controls in
Dialog Boxes. Also follow the specific guidelines for check boxes
presented in this section.
NOTE
The recommendation for the placement of the check box and its label
may need to be modified for localization for different countries.
Recommended
If a set of check boxes are grouped together under a header, the header
label for the group should indicate the category of variables that are
being defined by the buttons.
Recommended
Place the header for a set of check boxes above the group of check boxes.
Required
Label each check box to indicate the particular variable that is being
toggled on or off.
296
Chapter 9
Recommended
If space is available and it will not distort the meaning of the controls, all
check boxes within a window should be grouped together and vertically
aligned:
When check boxes are vertically aligned, the indicators should be
aligned and the labels should be left aligned relative to one another.
If check boxes are on the left side of a window, left align all state
indicator buttons no less than 1/3 inch and no more than 1/2 inch, or
14 base dialog units, from the inside edge of the window border.
Vertically aligned check boxes are easier for users to scan than
horizontally aligned buttons.
Optional
Required
Recommended
On initial presentation, each check box should be set to the value that
would most likely be selected by the user.
Text Boxes
Text boxes are controls that present textual data, or fields into which the
user can type characters from the keyboard. Text boxes can be combined
with menus, lists, and other selection mechanisms, such as the radio
buttons, to allow users increased flexibility with ease of use. Examples of
variables that can best be presented in text boxes are names, comments,
and locations.
Chapter 9
297
Recommended
The use of a text box is recommended when most or all of the following
conditions are met:
The desired result is the providing unspecified information, making of
a choice, the setting of a state or the giving of a command.
The set of possible valid entries is large.
Entries cannot all be predefined in advance.
Users will know what entries are valid.
The control is to be used as part of a keyboard intensive task.
Any input is acceptable (for example, a comment field).
Placement and Labeling
Follow the general guidelines for the placement and labeling of controls
presented in this chapter under General Guidelines for Controls in
Dialog Boxes. Also follow the specific guidelines for text boxes presented
in this section.
NOTE
The recommendation for the placement of text box and its label may
need to be modified for localization for different countries.
Recommended
Label text boxes to clearly indicate the purpose and meaning of the
control. Include valid ranges in labels where appropriate; for example,
Page Width (60-120).
298
Chapter 9
Required
If there is a wide variation in the length of labels, place labels above the
text box.
Labels above text box allow for easier localization.
Required
If labels are placed above text boxes, align the left edge of the first
character in the label with the left edge of the text box beneath it.
Required
If labels are placed to the left of text boxes, right-align labels with the left
edge of the text field.
Required
If there are multiple rows of text boxes, vertically align the boxes of these
fields.
General Guidelines
Required
Recommended
Recommended
The location of the text cursor when a text box is first given keyboard
focus should support the users task:
If the task flow indicates that a portion of the text in the box is most
likely to be modified, then the text cursor should be placed at the end
of that portion.
Example: A server and its fully distinguished name are displayed in
a text box. The text cursor is placed at the end of the hostname, before
the domain name, as this is the portion of the name most likely to be
changed.
If the task flow indicates that no specific portion of the text is most
likely to be modified, the text cursor should be placed at the end of the
text in the box.
Chapter 9
299
NOTE
If the entire text is selected for replacement it is possible that the text
cursor will not be shown.
Recommended
If the users task will typically require the replacement of all rather than
a portion of the text in a text box, the entire text should be selected for
replacement when the user first enters that text box.
If the user enters information into the text box, the previously
selected text should be replaced with the new text.
If the user leaves the text box without entering new information, the
text that was initially in the box should remain.
Size of Text Boxes and Scrolling
Required
Use single-line text boxes only if users are limited to entering characters
equal to one line or less.
Users should not be able to press the Return key and get a new line
within a single line text field.
Required
If users can enter multiple lines of text into a single text box, make the
default size of the text box show multiple lines (that is, two lines or
more).
Recommended
Recommended
Recommended
A mono-spaced font should be used for the data in the text box so that
the text box will appear to be filled when the maximum number of
characters has been entered into the box.
300
Chapter 9
Single-line text boxes can scroll if there is more information in the box
than can be viewed within the visible area of the text box.
Recommended
Provide vertical scroll bars for multiple line text boxes, only after the
user has entered more lines of text than can be viewed within the visible
area of the text box.
Default Action and Default Values
Recommended
If the location cursor is in a single line text box and there is a push
button associated with the text box, the default action should be to
activate the push button. The location cursor should remain in the text
box.
Recommended
If the location cursor is in a single line text box and the text box does not
have an associated push button, the default action should be to move to
the next input field, if one exists.
Recommended
If the location cursor is in a multi-line text box, the text cursor should
move to the next line in the text box when the user presses Enter. The
location cursor should remain on the text box.
Recommended
Whenever possible, provide a default value for text boxes. The default
value should be the value most likely to be entered by users.
Even if the value needs to be changed by the many users, it will provide a
indication of the format required for the entry.
Recommended
If there is no meaningful default value can be provided for a text box, the
box should be empty.
Combo Boxes
Combo boxes are controls that combine text boxes and lists of items.
There are two types of combo boxes, regular and drop-down combo boxes.
In regular combo boxes the list is continually presented below the text
field in which users can enter data. Drop-down combo boxes present only
the text field until the user takes an action to present the list.
Chapter 9
301
Recommended
The use of a combo box is recommended when most or all of the following
conditions are met:
The desired result is the making of a choice or the setting of a state.
Choices are mutually exclusive.
There is limited display space.
Users need to see only the item that is currently selected, except
when changing the selection.
There are 5 or more items to choose from or the number of items may
change over time.
Users may be able to type the entry more quickly than they can select
it.
The control is used as part of a keyboard intensive task.
Users may have to type values that cannot be supplied by the
application.
Recommended
Use drop-down combo boxes to replace option buttons from Motif when
running on the Windows NT operating system.
Placement and Labeling
Follow the general guidelines for the placement and labeling of controls
presented in this chapter under General Guidelines for Controls in
Dialog Boxes. For specific guidelines on the labeling and placement of
combo boxes see Text Boxes.
302
Chapter 9
If combo box list does not present an exhaustive list of all valid
alternatives, allow the user to type values that are not currently in the
list. Valid typed values should be added to the list whenever possible.
Recommended
If combo boxes are used and space is not an issue, use regular combo
boxes where the list is always available.
Recommended
Combo boxes should provide automatic searching of the list entries based
on the characters that the user types into the text box. This aids users in
searching for items in long lists and allows for consistency across all
combo boxes. Searches should take into account all characters typed by
the user, not only the first character.
Required
When combo boxes are used they should provide the same visual cues
that are recommended for text controls and for list boxes (see Text
Boxes and List Boxes).
Default Action and Default Values
Recommended
If the location cursor is on the text box portion of the combo box, the
default action should be to check the entry in the text box, and if it is
valid, move to the next field. If the entry is not valid, an error message
should be given and the location cursor should remain in the combo box.
Recommended
The default value in a combo box should be the value most likely to be
chosen by users.
Spin Boxes
A spin box is a control with a text box and up and down arrows that the
user clicks to move through a fixed set of values. Users can also type
valid inputs into the text box associated with the control.
Recommended
The use of a spin box is recommended when most or all of the following
conditions are met:
The desired result is the making of a choice or setting of a state.
Choices are mutually exclusive.
There is limited space.
Chapter 9
303
NOTE
The recommendation for the placement of the spin box and its label may
need to be modified for localization for different countries.
Required
Unless the values inside the spin box make the purpose of the spin box
intuitively obvious, each spin box should have a label to indicate
particular variable that is being incremented or decremented by the spin
box. See Figure 9-7 and Figure 9-8.
Figure 9-7
Figure 9-8
Recommended
The label for the spin box should be to the left of the spin box or above
the spin box.
Optional
If it will benefit the user, place labels identifying units for variables
inside the spin box or to the right of the spin box.
Recommended
The mapping between the labels on the buttons and the direction of
change in values should be consistent with user population conventions.
304
Chapter 9
Recommended
The default value in a spin box should be the value most likely to be
chosen by users.
Figure 9-10
Chapter 9
305
NOTE
The recommendation for the placement of an analog control and its label
may need to be modified for localization for different countries.
Required
Both ends of the scale associated with a slider or gauge must be labeled
so that users can determine the direction of the continuum for increasing
and decreasing values. See Figure 9-9.
Recommended
If users will need to know the absolute value for the variable set by the
slider or gauge, provide a label that displays the value. See Figure 9-9
and Figure 9-10.
Recommended
306
Chapter 9
Place the label identifying the type of variable to left or above the slider
or gauge.
Recommended
If it will benefit the user, display a default setting for the slider as a more
elongated marking on the scale, see Figure 9-9.
Recommended
If it will benefit the user, display threshold settings for the gauge as a
line or a change in coloring inside the main portion of the gauge, see
Figure 9-10.
Default Action and Default Values
Required
Recommended
List Boxes
Lists can have a single dimension or multiple dimensions. Lists that
have a single dimension are typically presented in a list box with each
item in the list appearing as a row in the list box. Different dimensions of
a multiple dimension list are typically presented as different columns
within a row that represents the item. Guidelines on presenting single
column lists in list boxes are presented in this section of the style guide.
Guidelines for multiple dimension lists are presented in section on
Tables and Grids later in this chapter.
List boxes can allow users to select a single item or multiple items from
within the list. Lists can have both horizontal and vertical scroll bars for
scrolling the visible portion of the list of items.
When to Use
Recommended
The use of a single selection list box is recommended when most or all of
the following conditions are met:
Chapter 9
307
NOTE
If a vertical scroll bar will be used with the list box, it is important that
the list box be large enough to show at least 3 items.
Recommended
NOTE
308
Chapter 9
NOTE
The recommendation for the placement of list boxes and their labels may
need to be modified for localization for different countries.
Required
Label lists to clearly indicate the purpose and content of the list. Label
the items contained in lists to clearly identify them to the user.
Recommended
Recommended
Required
Chapter 9
309
Recommended
NOTE
In a single selection list box, the default action should be to perform the
action most frequently associated with the list item, that is, select, open,
modify. After the default action, location cursor should either remain at
its current location or move to the next input field.
The location cursor should remain at its current location if the default
action was to bring up a dialog box.
The location cursor should move to the next field if the default action
was the selection of the list item.
Recommended
In a multiple selection list box, the default action should be select the list
item and move to the next list item that is available for selection or
deselection.
Recommended
In a single selection list box, the initial default selection should be either
the item most likely to be selected or the first item in the list.
310
Chapter 9
In a multiple selection list box, the default selection should include the
set of items most likely to be selected by the user.
Follow the guidelines in this section when using tree list controls.
When to Use
Recommended
The tree list control is recommended when most or all of the following
conditions are met:
The desired result is the making of a choice or the setting of a state.
There is value in showing the hierarchical relationships between the
items in the hierarchy or items can be meaningfully grouped in a
hierarchy.
Users need to select all of the subordinates of one or more levels in
the hierarchy.
There are a large number of items and users can get lost in the
information if some of the items are not hidden from initial view.
The number of items may change over time.
Chapter 9
311
NOTE
The recommendation for the placement of tree lists and their labels may
need to be modified for localization for different countries.
Recommended
Label tree list items meaningfully to indicate the specific objects in the
list.
Recommended
If icons are used in the list, place the icons to the right of the [+] and [-]
expansion controls and place the labels to the right of the icons. If icons
are not used in the list, place the labels to the right of the [+] and [-]
expansion controls
General Guidelines
Recommended
Recommended
Indent each level in the hierarchy to indicate lower-level items that are
subordinate to a higher-level item.
Recommended
Chapter 9
In single selection tree lists and tree lists used in the scope pane, the
currently selected items should be marked by a selection highlight (blue
background with white text) see the left portion of Figure 9-12.
Recommended
NOTE
If single selection is the most typical type of selection done in a tree list
control, check boxes are not recommended.
Optional
If there are a significant number of levels in the hierarchy and space for
the check boxes is an issue, multiple selection can be done by:
Substituting check boxes for icons.
Substituting check boxes for expansion controls.
NOTE
Check boxes that replace the expansion control are not allowed for
multiple selection in a tree list control in a scope pane. Having expansion
Chapter 9
313
Tree lists with check boxes allow users to select objects at different levels
in the hierarchy. This type of selection allows the selection to be
inherited by objects lower in the hierarchy. Users should be able to
control selection at each level in the hierarchy.
Required
If the user selects an item at a higher level in the hierarchy, all items
contained within the higher level item should be marked as selected
(that is, black check mark in their check boxes).
Required
When the user selects a subset of items beneath a higher level item or
turns off some of the selections that were done by means of selecting a
higher level item, the check mark in the check box of the higher level
item should be light gray instead of black to indicate that the item is
partially selected.
Recommended
314
Chapter 9
Required
Clicking on the check box or on the icon to make the item part of a
multiple selection should not affect the position of the selection cursor or
location cursor if the tree list is presented in the scope pane.
Keyboard Navigation in Tree List Controls
Recommended
Pressing the down arrow key acts to move the selection cursor down and
to execute any action associated with selection. When at the bottom of
the hierarchy, pressing the down arrow key does nothing.
Recommended
Pressing the up arrow key acts to move the selection cursor up and to
execute any action associated with selection. When at the top of the
hierarchy, pressing the up arrow key does nothing.
Recommended
Recommended
315
A single click on the [+] or [-] causes the item to expand or contract
depending on its previous state.
Required
A single selection button click on the icon or the item label, selects the
item and executes any action associated with the selection.
Recommended
Double-clicking on the icon or the item label that has a [+] or [-] causes
the item to expand or contract depending on its previous state, selects
the item and executes the default action associated with the item.
Recommended
A menu button click on the item results in a pop-up menu with menu
items that are specific to the item under the pointer.
Recommended
If the names of the item in the tree list are truncated, resting the pointer
over the name of the item should result in the presentation of a tooltip
with the full name of the item.
Default Actions and Default Values
The default action associated with items in a tree list control will vary
depending on how the control is being used. Typical default actions are to
open the item, expand and open the item, or open a properties dialog
associated with the item.
Recommended
If appropriate to the use of the tree list control, items in the list are
recommended to have default actions associated with them.
Recommended
In a single selection tree list, the initial default selection should be either
the item most likely to be selected or the first item in the list.
Recommended
In a multiple selection tree list, the default selection should include the
set of items most likely to be selected by the user.
316
Chapter 9
Table
Chapter 9
317
Grid
Recommended
Chapter 9
NOTE
The recommendation for the placement of an tables and grids and their
labels may need to be modified for localization for different countries.
Recommended
In tables and grids, vertically align the label for the first column with the
left side of the list box. For the labels for the remaining columns, follow
these guidelines:
If the contents of a line in the column is long relative to the label (for
example, if the line in the column contains 50 characters and spaces
and the label contains 10), center the label above the column unless
this would cause the label to be off the visible area of the display
when a portion of the column is displayed.
If the contents of the column is approximately the same width as, or
shorter than, the label, the label should be left aligned.
Recommended
Recommended
Tables should have a column label above each column in the table. If
users can horizontally scroll the data, they should be able to scroll the
column labels.
Chapter 9
319
Tables should have the appearance of a multiple column list and there
should not be any lines between the rows and columns in the table.
Recommended
Recommended
If the content of the table or grid is greater than can fit on a single screen
of information, allow users to resize the columns of information to meet
their individual needs. Also consider giving the user control over the
sequencing of the columns of information.
Recommended
Push buttons that act on selections within the table should be placed to
the right of the table.
If users will need to edit or modify the entries in the table, provide a
push button labeled Modify... or Properties... that will present a
separate dialog box for editing a given row in the table. Each editable cell
in the table should be represented by a separate field in the dialog box.
Recommended
When a table first receives input focus, the row that the user is most
likely to select or modify should be selected.
Recommended
When a grid first receives input focus, the cell that the user is most likely
to edit should have input focus.
If the most likely user action is to add entries to the grid, the cell with
input focus should be the left most cell within the first empty row of the
grid.
Recommended
If the grid is the only control in a dialog box or window, input focus
should on the grid and one of the cells in the grid should have input focus
when the window is first opened.
Required
The cell in the grid that has input focus should be indicated by a clear
visual cue. A dark border around the cell is the suggested visual cue. See
Figure 9-15.
320
Chapter 9
Grids in which users can add entries should have two empty rows of cells
at the bottom. See Figure 9-15.
Having two empty rows in the grid provides a visual cue that users can
add new entries to the table. After the user has filled in information in
the first empty row and then moves to the second empty row a new
empty row of cells should be added to the grid. This assures that there is
always an empty row of cells at the bottom of the grid, even when the
user is doing data entry in the last column of the empty row.
Recommended
When the user is adding a new item to an grid, default values should be
provided in cells where it is possible to have default values.
Recommended
Required
If some of the cells in the grid are read only this should be indicated by a
grayed background appearance to the cells. See Figure 9-15.
Recommended
If controls other than text boxes are placed in the cells of grids, the
controls should not be visible until input focus is in the cell.
If input focus is not in one of the cells in the grid, the cells should only
reflect the current value of that cell. When input focus is placed within
the cell the type of control associated with that cell should be shown.
Filtering and Sequencing of Items
The best sequencing of the items in a table or grid depends on the nature
of the objects represented in the table.
Recommended
When it will benefit the users task, users should be able to filter the
information in the table or grid.
Typically filtering capabilities can be accessed by a pop-up menu
associated with the column labels for the table or grid.
Recommended
When users can add entries to tables or grids, the entries should be
sequenced in the order in which they were added.
Recommended
Chapter 9
321
When it will benefit the users task, users should be able to control the
sequence of items in the table:
Sort the tabular information by the information in the various
columns by clicking on the column labels.
Resequence the columns in the table by dragging the column heading
to a new location.
Resequence rows in the table by selecting the row and dragging it to a
new location or by push buttons for manipulating item sequence (for
example, [Move Up] and [Move Down].
Recommended
If a table or grid has more columns than can be displayed in the dialog
box or window in which it is contained, a horizontal scroll bar should be
provided to allow users to see all of the columns.
Recommended
If a table or grid has more rows than can be displayed in the dialog box or
window in which it is contained, a vertical scroll bar should be provided
to allow users to see all of the rows.
Selection in Tables and Grids
Recommended
Recommended
Unless users are able to select individual cells in the table, the selection
highlight should be placed around the full row in the table when the user
selects it.
Recommended
Recommended
In a table:
Pressing the down arrow key should move the selection cursor down
one row. When at the last row in the table, pressing the down arrow
key does nothing.
322
Chapter 9
In a grid:
Pressing the Down Arrow key should move input focus down one row.
When at the last row in the table, pressing the Down Arrow key does
nothing.
Pressing the Up Arrow key should move input focus up one row.
When at the first row in the table, pressing the Up Arrow key does
nothing.
Pressing the Right Arrow key should move input focus to the next
editable cell in the table. When at the last editable cell in the table,
pressing the Right Arrow key does nothing.
Pressing the Left Arrow key should move input focus to the previous
editable cell. When at the first editable cell in the table, pressing the
Left Arrow key does nothing.
Default Actions and Default Values
Recommended
When one or more rows are selected in a table, the default action should
be to perform the most typical action associated with the item associated
with the table row (for example, open, modify).
In Figure 9-14 the default action would be to enable the selected object.
Recommended
When in the cell of a grid, the default action should be to perform the
most typical action associated with the cell.
Chapter 9
323
If users will need to take action on items in a table, the item that users
will most likely need to act on should be selected. If there is no means for
determining what item users will need to act on, the first item in the
table should be selected.
Tab Controls
Tab controls provide a means of presenting a large amount of
information in a limited amount of space. These controls present
multiple pages of information or controls using a metaphor of a set of
index cards with attached tabs.
Figure 9-16
Tab Control
324
Chapter 9
NOTE
The recommendation for the placement of tab controls and their labels
may need to be modified for localization for different countries.
Recommended
Recommended
The sequence of tabs within a tabbed control should match the logical
order required by the users task:
The most frequently used tabs should be placed to the left in the
sequence and less frequently used tabs should be placed to the right.
Data that users would expect to provide first are placed in the first
tab in the sequence (for example, the name of the item or object).
Chapter 9
325
Recommended
Recommended
Figure 9-17
Vertical Tabs
326
Chapter 9
NOTE
General Guidelines
Recommended
Recommended
Recommended
If there are more categories than there is space for tabs in a single row
the following methods should be used to eliminate the need for multiple
rows of tabs:
Using the shortest possible meaningful tab label and shrinking the
tabs to fit the labels.
Restructuring the categories so there are fewer categories.
Increasing the width of the tabbed dialog box so that there is more
space for tabs.
Scrolling the tabs if user performance will not suffer from seeing a
subset of the categories.
Recommended
Chapter 9
327
Scrollable Tabs
Recommended
Required
Tabs in a tab control that may be unavailable for long periods of time or
may never be available (that is, tabs only available when specific
software has been installed or if the operator is granted specific
permissions) should be removed from the tab control. These tabs should
only be included in the tab when the prerequisites for their availability
have been met.
Required
Push buttons that act on a single tab with the set of tabs should be
placed within the tab on which they act.
Required
Push buttons that act on all of the tabs within a tab set should be placed
outside of the tabs.
NOTE
Push buttons placed outside of the tab set should be placed beneath the
set of tabs or optionally to the side of the tabs. Placement beneath the set
of tabs is preferred.
328
Chapter 9
Grouping Controls
In addition to providing aesthetic appeal, grouping of information can
aid user recall, and result in faster screen search. Grouping methods
include separator lines, group boxes, and panes.
Separator lines are simply a horizontal or vertical line that is used to
separate information on the screen. Separator lines are commonly used
in menus to separate different types of menu items. They can also be
used in windows and dialog boxes to separate different types of controls.
Separator lines take up less space than group boxes as they consist of a
single line rather than a set of four lines.
Figure 9-19
NOTE
Group boxes provide a box or line surrounding the set of controls that
they group. Group boxes can be used to organize the screen or dialog box
into functional or semantic groups. Although technically considered
controls, group boxes do not process any mouse or keyboard input. They
Chapter 9
329
Panes provide a more definite boundary between the set of controls that
they group. Panes divide the window into individual segments and allow
the user to apportion the window display space based on their individual
needs when using the different window segments. The information
presented in a pane can be independently scrolled. Like group boxes,
panes affect the keyboard navigation within a window, as the user of the
interface must use the Tab key to move between the different panes in
the window. See Figure 9-21.
330
Chapter 9
When to Use
Recommended
Chapter 9
331
Recommended
332
Chapter 9
All controls and fields inside the group box should be meaningfully
related.
Required
Recommended
Recommended
The spacing and alignment of group boxes should adhere to the following
guidelines:
Maintain a consist spacing (4-7 dialog base units) above, below, to the
left, and the right of the controls and labels inside the group box.
Leave a minimum 7 base dialog units between the group box and the
edge of the window or dialog box in which it is contained.
Align the items within the group box (for example, left align check
boxes or radio buttons).
Recommended
Recommended
Chapter 9
333
Use panes with size controls to enable the user to adjust the relative size
of each pane to suit the current task.
Recommended
The default size of a pane should be sufficient for the user to easily access
and use all controls contained within the pane.
Optional
Recommended
334
Chapter 9
10
Miscellaneous Guidelines
335
Miscellaneous Guidelines
336
Chapter 10
Miscellaneous Guidelines
Internationalization and Localization of the User Interface
337
Miscellaneous Guidelines
Internationalization and Localization of the User Interface
338
Chapter 10
Miscellaneous Guidelines
Internationalization and Localization of the User Interface
Assume that the hostnames and UNIX login names contain strictly
7-bit characters (networking software does not allow multibyte
characters in those areas).
Do not assume that one column = one character. Most Asian
characters require two columns per character.
Do not use bold face and italic fonts to differentiate from non-bold and
non-italic fonts, or be sure that the fonts can be localized. Not all
multibyte fonts can be bold faced or italicized.
Do not assume that words are separated by a space. Some languages
do not separate words with a space character.
Do not assume that special characters (such as ?, !, ) exist within a
language.
Do not assume the existence of a period (.) to end a sentence. Some
languages do not end their sentences with a period.
Do not build English grammar into the user interface. For example, a
menu command that spells out the English sentence using a cascade
menu Display->data->using->graphs will be very difficult (if not
impossible) to localize. Another example of a non-localizable interface
is one that requires an end user to fill in the blanks, as in search for
______ in the _____ file.
Do not use X or check marks to imply OK or not OK; show legends for
symbols if necessary.
Do not use abbreviated English characters. For example, using D next
to map names to indicate the Default map is not intuitive to
non-English speaking users. Also, the letter D cannot be translated
easily.
Do not assume that short (or long) English words are short (or long)
words in other languages. Allow the user interface component (for
example, the text widget or the push-button widget) to shrink or
expand based on varying sizes of words.
Do not assume that the characters can be displayed using fonts
smaller than 14 pixels wide. For example, most Asian characters are
completely unreadable when displayed using fonts that are smaller
than 14 pixels wide.
Do not assume that American/Western color coding conventions (for
example, green = go or OK, blue ribbon = first place) will apply to
Chapter 10
339
Miscellaneous Guidelines
Internationalization and Localization of the User Interface
your customers. Allow users to customize the colors used in your
application.
Do not use graphics for symbols or icons that have the potential for
offending user, or that have different meanings in different cultures.
For example, graphics that contain body parts, such as a hand, may
be viewed as offensive in some cultures. As another example, in the
US, a black cat is a symbol of bad luck, while in the UK it is a symbol
of good luck.
340
Chapter 10
11
341
342
Chapter 11
Types of Documentation
HP identifies six basic types of manuals, which define a basic structure
for meeting the needs of users, based on their knowledge level and
learning needs.
Quick Start Guidea one-glance overview of the product and a few
task instructions to help the user get comfortable.
Task Referencea complete set of task instructions and
problem-solving guidelines, with a few basic concepts. This is often
the basis for a Users Guide.
Reference Guidedescriptions of the product in a dictionary or
encyclopedia format.
Concept Guidetopics that explain concepts and apply them to
advanced tasks.
Installation Guideinstructions for installing and configuring the
product.
Quick Referencetables, syntax lists, menu trees, and brief
instructions that help the user remember details.
A Modular Approach
Start by identifying the information that is most important for the type
of manual. This information may be task or tutorial instructions,
Chapter 11
343
Task Module 3
Task Module 2
Task Module 1
Problem Module 3
Problem Module 2
Problem Module 1
Topic Module 3
Topic Module 2
Topic Module 1
Concept Module 3
Concept Module 2
Concept Module 1
Chapter 11
Chapter 11
345
346
Chapter 11
Chapter 11
347
348
Chapter 11
Chapter 11
349
350
Chapter 11
HP OpenView Launcher
Categories
351
352
Appendix A
Appendix A
353
354
Appendix A
Appendix A
355
356
Appendix A
Appendix A
357
358
Appendix A
359
Table B-1
Table B-2
Meaning
Ctrl + C
Copy
Ctrl + O
Open
Ctrl + P
Ctrl + S
Save or Apply
Ctrl + V
Paste
F1
Help
Esc
Cancel
Alt + Enter
Shift + F10
About
Action
Apply
Save As
Select All
Back
Close
Copy
Delete
Edit
Explore
360
Appendix B
Table B-2
File
Find
Finish
Help
Hide
Move
New
Next
Open
Paste
Quick Navigator
Properties
Refresh
Save
Show
Cut
Help Topics
View
Window
Exit
Appendix B
361
362
Appendix B
363
NOTE
The limited palette is a subset of the expanded palette. This means that
the color values in the limited palette are also included in the expanded
palette.
Palette Contents
In the next two sections, the color values for each palette are listed in a
table. For each color value, you will see a column for its hexadecimal
value and a column for its decimal value. Browsers typically require
color values to be stated in hexadecimal. Conversely, many graphics
editing programs use digital (decimal) values for their RGB values.
364
Appendix C
NOTE
Appendix C
365
Color
Name
Hex
Value
Decimal
Value
Blue
00 00 FF
0 0 255
Green
00 FF 0
0 255 0
Normal status
Red
FF 0 0
255 0 0
Critical status
Yellow
FF FF 00
255 255 0
Minor status
Orange
FF 80 00
255 128 0
Major status
Dark Blue
00 00 80
0 0 128
Selection indication
Dark Green
00 80 00
0 128 0
Dark Red
80 00 00
128 0 0
Gold
80 80 00
128 128 0
Dark Brown
64 00 00
100 0 0
Disabled status
Light Blue
00 80 FF
0 128 255
Unknown status
Cyan
00 FF FF
0 255 255
Warning status
Magenta
FF 00 FF
255 0 255
Light Pink
FF 80 FF
Restricted status
Tan
FF BF 66
Testing status
Teal
00 80 90
0 128 128
Purple
80 00 80
128 0 128
Off-white
FF FF CC
Unmanaged status
White
FF FF FF
366
HP OpenView usage
(other than icons)
Appendix C
Color
Name
Hex
Value
Decimal
Value
HP OpenView usage
(other than icons)
Gray (0) a
C0 C0 C0
Gray (1) b
CB CB CB
Gray (2) b
98 98 98
Gray (3) b
66 66 81
Gray (4)
33 33 4F
51 51 79
Black
00 00 00
000
Text
Appendix C
367
NOTE
Hex Value
Decimal Value
00 00 00
000
Row 1 , Column 1
0 0 33
0 0 51
Row 1 , Column 2
0 0 66
0 0 102
Row 1 , Column 3
00 00 80
0 0 128
Row 1 , Column 4
368
Appendix C
Hex Value
Decimal Value
0 0 99
0 0 153
Row 1 , Column 5
0 0 CC
0 0 204
Row 1 , Column 6
0 0 ED
0 0 237
Row 1 , Column 7
00 00 FF
0 0 255
Row 1 , Column 8
0 40 0
0 64 0
Row 1 , Column 9
0 40 33
0 64 51
Row 1 , Column 10
0 40 66
0 64 102
Row 2 , Column 1
0 40 99
0 64 153
Row 2 , Column 2
0 40 CC
0 64 204
Row 2 , Column 3
0 40 FF
0 64 255
Row 2 , Column 4
0 80 0
0 128 0
Row 2 , Column 5
0 80 33
0 128 51
Row 2 , Column 6
0 80 66
0 128 102
Row 2 , Column 7
0 80 80
0 128 128
Row 2 , Column 8
0 80 99
0 128 153
Row 2 , Column 9
0 80 CC
0 128 204
Row 2 , Column 10
0 80 FF
0 128 255
Row 3 , Column 1
00 FF 00
0 255 0
Row 3 , Column 2
0 FF 33
0 255 51
Row 3 , Column 3
0 FF 66
0 255 102
Row 3 , Column 4
0 FF 99
0 255 153
Row 3 , Column 5
0 FF CC
0 255 204
Row 3 , Column 6
00 FF FF
0 255 255
Row 3 , Column 7
Appendix C
369
Hex Value
Decimal Value
33 33 4F
51 51 79
Row 3 , Column 8
40 0 0
64 0 0
Row 3 , Column 9
40 0 33
64 0 51
Row 3 , Column 10
40 0 66
64 0 102
Row 4 , Column 1
40 0 99
64 0 153
Row 4 , Column 2
40 0 CC
64 0 204
Row 4 , Column 3
40 0 FF
64 0 255
Row 4 , Column 4
40 40 0
64 64 0
Row 4 , Column 5
40 40 33
64 64 51
Row 4 , Column 6
40 40 66
64 64 102
Row 4 , Column 7
40 40 99
64 64 153
Row 4 , Column 8
40 40 CC
64 64 204
Row 4 , Column 9
40 40 FF
64 64 255
Row 4 , Column 10
40 80 00
64 128 0
Row 5 , Column 1
40 80 33
64 128 51
Row 5 , Column 2
40 80 66
64 128 102
Row 5 , Column 3
40 BF 0
64 191 0
Row 5 , Column 4
40 BF 33
64 191 51
Row 5 , Column 5
40 BF 66
64 191 102
Row 5 , Column 6
40 BF 99
64 191 153
Row 5 , Column 7
40 BF FF
64 191 255
Row 5 , Column 8
40 FF 00
64 255 0
Row 5 , Column 9
40 FF 33
64 255 51
Row 5 , Column 10
370
Appendix C
Hex Value
Decimal Value
40 FF 66
64 255 102
Row 6 , Column 1
40 FF 99
64 255 153
Row 6 , Column 2
40 FF CC
64 255 204
Row 6 , Column 3
40 FF FF
64 255 255
Row 6 , Column 4
55 1A 8A
85 26 138
Row 6 , Column 5
64 00 00
100 0 0
Row 6 , Column 6
66 66 81
Row 6 , Column 7
80 00 00
128 0 0
Row 6 , Column 8
80 00 33
128 0 51
Row 6 , Column 9
80 00 66
128 0 102
Row 6 , Column 10
80 0 80
128 0 128
Row 7 , Column 1
80 00 99
128 0 153
Row 7 , Column 2
80 00 CC
128 0 204
Row 7 , Column 3
80 00 FF
128 0 255
Row 7 , Column 4
80 40 00
128 64 0
Row 7 , Column 5
80 40 33
128 64 51
Row 7 , Column 6
80 40 66
128 64 102
Row 7 , Column 7
80 40 99
128 64 153
Row 7 , Column 8
80 40 CC
128 64 204
Row 7 , Column 9
80 40 FF
128 64 255
Row 7 , Column 10
80 80 00
128 128 0
Row 8 , Column 1
80 80 33
128 128 51
Row 8 , Column 2
80 80 66
Row 8 , Column 3
Appendix C
371
372
Hex Value
Decimal Value
80 80 99
Row 8 , Column 4
80 80 CC
Row 8 , Column 5
80 80 FF
Row 8 , Column 6
80 FF 0
128 255 0
Row 8 , Column 7
80 FF 33
128 255 51
Row 8 , Column 8
80 FF 66
Row 8 , Column 9
80 FF 99
Row 8, Column 10
80 FF CC
Row 9 , Column 1
80 FF FF
Row 9 , Column 2
98 98 98
Row 9 , Column 3
BF 0 0
191 0 0
Row 9 , Column 4
BF 0 33
191 0 51
Row 9 , Column 5
BF 0 66
191 0 102
Row 9 , Column 6
BF 0 99
191 0 153
Row 9 , Column 7
BF 0 CC
191 0 204
Row 9 , Column 8
BF 0 FF
191 0 255
Row 9 , Column 9
BF 40 0
191 64 0
Row 9 , Column 10
BF 40 33
191 64 51
Row 10 , Column 1
BF 40 66
191 64 102
Row 10 , Column 2
BF 40 99
191 64 153
Row 10 , Column 3
BF 40 CC
191 64 204
Row 10 , Column 4
BF 40 FF
191 64 255
Row 10 , Column 5
BF 80 0
191 128 0
Row 10 , Column 6
Appendix C
Hex Value
Decimal Value
BF 80 33
191 128 51
Row 10 , Column 7
BF 80 66
Row 10 , Column 8
BF 80 99
Row 10 , Column 9
BF 80 CC
Row 10 , Column 10
BF 80 FF
Row 11 , Column 1
BF FF 0
191 255 0
Row 11 , Column 2
BF FF 33
191 255 51
Row 11 , Column 3
BF FF 66
Row 11 , Column 4
BF FF 99
Row 11 , Column 5
BF FF CC
Row 11 , Column 6
BF FF FF
Row 11 , Column 7
C0 C0 C0
Row 11 , Column 8
CB CB CB
Row 11 , Column 9
FE 00 00
254 0 0
Row 11 , Column 10
FE FE CB
Row 12 , Column 1
FF 00 00
255 0 0
Row 12 , Column 2
FF 0 33
255 0 51
Row 12 , Column 3
FF 0 66
255 0 102
Row 12 , Column 4
FF 0 99
255 0 153
Row 12 , Column 5
FF 0 CC
255 0 204
Row 12 , Column 6
FF 00 FF
255 0 255
Row 12 , Column 7
FF 40 0
255 64 0
Row 12 , Column 8
FF 40 33
255 64 51
Row 12 , Column 9
Appendix C
373
Hex Value
Decimal Value
FF 40 66
255 64 102
Row 12 , Column 10
FF 40 99
255 64 153
Row 13 , Column 1
FF 40 CC
255 64 204
Row 13 , Column 2
FF 40 FF
255 64 255
Row 13 , Column 3
FF 80 0
255 128 0
Row 13 , Column 4
FF 80 33
255 128 51
Row 13 , Column 5
FF 80 66
Row 13 , Column 6
FF 80 99
Row 13 , Column 7
FF 80 CC
Row 13 , Column 8
FF 80 FF
Row 13 , Column 9
FF BF 66
Row 13 , Column 10
FF FF 0
255 255 0
Row 14 , Column 1
FF FF 33
255 255 51
Row 14 , Column 2
FF FF 66
Row 14 , Column 3
FF FF 99
Row 14 , Column 4
FF FF CC
Row 14 , Column 5
FF FF FF
Row 14 , Column 6
374
Appendix C
Bibliography
375
Bibliography
376
Appendix D
Bibliography
Appendix D
377
Bibliography
378
Appendix D
Index
A
accelerators, 125
actions
representing with symbols,
188
alignment
in dialog boxes, 269
analog conrols
guidelines, 297
analog control
guidelines, 296, 297
analog controls
guidelines, 295
placement, 296
when to use, 296
application registration files,
118, 131
applications
accessing from keyboard, 31
quick access to, 31
usability principles, 29
audio
using to provide cues, 31
C
chart presentation format, 156
check box
default action, 287
default value, 287
guidelines, 286287
label, 286
placement, 286, 288
when to use, 286
child window
selection, 222, 226
color
coding, 31
Java System Color Variables,
57
link color, 55
colors
in web applications, 55
Index
controls, 263
analog controls, 295
check box, 286
default values, 272
ellipsis in, 271
gauge, 295
graying, 271
grouping, 319
input validation, 274
labeling, 270
punctuation in label, 270
push button, 277
radio buttons, 284
See also specific type, 277
slider, 295
spin box
, 293
text box, 289
visual cues for, 270
conventions
typographical, 13
cues
filling connection symbols, 261
flashing symbols, 256
for drag and drop, 234
for recursive selection, 229
highlighting, 255
in graphics, 198
in menus, 123
in navigation tabs, 162
in the scope pane, 143
status colors, 245
symbol alerts, 249
transparent symbols, 257
customization
description bar, 133
toolbars, 130
D
default action
check box, 287
combo box, 293
379
Index
gauge, 297
grid, 313
lists, 300
multiple selection list, 300
of option buttons, 284
push button, 281
radio buttons, 285
single selection list, 300
slider, 297
spin box, 295
table, 313
text box, 291
tree list, 306
default actions
use of, 275
default value
check box, 287
combo box, 293
gauge, 297
option button, 284
radio buttons, 285
slider, 297
spin box, 295
text box, 291
default values
controls, 272
list box, 300
table, 314
tree list, 306
description bar, 133
customization, 133
dialog boxes, 263
alignment, 269
complexity, 271
controls, 277324
design, 265
field sequencing, 269
focus, 265
help, 268
menus, 266
modal and modeless, 272
push button placement, 278
380
resizing
, 268
size, 267
title bar, 265
documentation
accessing information in, 337
designing for audience, 335
guidelines for structure, 333
localizing, 339
organizing, 333
recommended contents, 337
specific guidelines, 335
types of manuals, 333
double clicking
affect on selection, 224
drag and drop, 234
changes in instrumentation
space, 239
containers as drop targets, 237
drop target help (OVW), 240
executable symbols (OVW),
240
executable symbols as drop
targets, 238
in OpenView Windows, 239
leaf level symbols as drop
targets, 238
views as drop targets, 235
visual cues, 234
E
ellipses, on button labels, 271
events
using vs. visual cues, 244
exception driven approach, 21
executable symbols
appearance, 259
F
field
defaults, 272
fields
alignment, 269
input validation, 274
labeling, 270
text box, 289
filter
grid, 311
table, 311
filters
in the scope pane, 146
focus
in dialog boxes, 265
font size
in dialog boxes, 266
windows, 266
fonts
in web applications, 60
form presentation format, 157
for properties, 159
forms
in web applications, 66
frames
in web applications, 63, 65
G
gauge
default action, 297
default value, 297
guidelines, 295, 297
labels, 296
placement, 296
gauges
when to use, 296
geometry, 215
graphical presentation format,
151
graphics, 171, 197
creating, 204
cues for classes, 193
for actions, 205
in HP OpenView Launcher, 45
in toolbar buttons, 129
in web applications, 60
Index
Index
localization, 205
overlay, 207
see also symbols, 171
size, 204
using existing, 197
visual cues, 198
grid
default action, 313
editing cells, 310
filter, 311
guidelines, 307314
input focus, 310
keyboard navigation, 313
labels, 309
placement, 309
selection, 312
sequencing, 311
when to use, 308
group boxes, 323
group selection, 228
using containers, 229
grouping
controls, 319
guidelines, 319324
use of group box, 322
use of line separator, 321
use of panes, 322
groups
concepts, 28
guage
guidelines, 296
H
help, 126
on dialog boxes, 268
highlighting symbols, 255
reporting status with, 255
HP OpenView Web Launcher
see web launcher, 39
HTML
using for web applications, 65
Index
I
iconic presentation format, 151
iconic presentation formats, 171
layout algorithms, 182
icons
see symbols, 171
images
in web applications, 60
independent views, 182
information coding principles,
30
information presentation
managers, 86
results pane, 88
scope pane, 88
when to use, 87
information update
in web applications, 63
input validation, 274
J
Java applets, 49
in Java Frame, 49
in web browser, 50
Java applications and applets,
67
K
keyboard access
in menus, 124, 125
keyboard navigation
in a grid, 313
in a table, 312
in a tree list, 305
in iconic presentation format,
151
in the scope pane, 137
keyboard, to access application
actions, 31
L
labels
capitalization, 270
check box, 286
combo box, 292
combo boxes, 292
controls, 270
for application actions, 32
gauge, 296
grid, 309
in navigation tabs, 165
list box, 299
menus, 122
option button, 283
push button, 279
radio buttons, 284
single selection list box, 299
slider, 296
spin box, 294
tab controls, 315
table, 309
text box, 288
tree list, 302
visual cues, 270
leaf level objects, 179
representation of, 173
list box
default action, 300
default values, 300
find capability, 299
guidelines, 297, 298, 299, 300,
301
labeling, 299
labels, 299
placement, 299
sequence of items, 299
use of multiple selection, 298
use of single selection, 297
lists
general guidelines, 299
guidelines, 301
logical sequence, 303
selection, 221
381
Index
File/container
menu,
109
general purpose menus, 110
sequence, 115
menus, 109
accelerators, 125
Action, 113, 117
affect of context, 117
application registration files,
118
depth/levels of menus, 121
Edit, 110
for managed objects, 112
for navigation tabs, 161
general purpose menus, 110
Help, 110
help for, 126
in dialog boxes, 266
in split windows, 99
labels, 122
mnemonics, 124
number of items, 120
pop-up/context, 116
separators, 124
sequence in menu bar, 115
structure, defining, 119
Tools, 117
View, 110
visual cues, 123
mnemonics, 124
382
Index
Index
table, 309
tree list, 302
pointer navigation
in a tree list, 306
pop-up menus, 116
in scope pane, 143
presentation formats
in the results pane, 149
presentation managers
concepts, 24
information presentation
managers, 86
multiple purpose presentation
managers, 89
object presentation managers,
77
task presentation managers,
79
presentation manages
use of information
presentation managers, 87
use of multiple purpose
presentation managers, 89
use of object presentation
managers, 77
use of task presentation
managers, 80
principles
for accessing actions, 31
for general usability, 29
for information coding, 30
for representing relationships,
32
progress indicator
in web applications, 51
properties
presentation of, 159
using a form presentation
format, 159
punctuation, in control label,
270
push button
at bottom of window, 278
Index
availability, 281
default action, 281
for whole dialog box, 278
guidelines, 277282
label, 279
placement, 278
sequence, 279
size, 279
visual cues for, 281
when to use, 277
Q
quick access
using navigation tabs, 160
R
radio button
guidelines, 286
radio buttons
default action, 285
default value, 285
guidelines, 284??
label, 284
placement, 285
when to use, 284
recursive selecton, 228
relationships
containment, 32
representing, 32
see connections, 187
results pane, 72, 148
chart presentation formats,
156
form presentation formats, 157
graphical presentation
formats, 151
in a task presentation
manager, 80
in an information presentation
manager, 88
in an multiple purpose
presentation manager, 90
in an object presentation
manager, 77
interaction with scope pane,
140
keyboard navigation, 151
presentation formats, 149
tabular presentation formats,
153
with icons, 151
S
scope pane, 137
general guidelines, 137
hierarchy, 138
in a multiple purpose
presentation manager, 90
in a task presentation
manager, 80
in an information presentation
manager, 88
in an object presentation
manager, 77
interaction with results pane,
140
keyboard navigation, 137
leaf level items, 140
pop-up menus, 143
visual cues, 143
with filters, 146
scope pane windows, 93
splitting, 98
when to use, 95
scoping pane
in web applications, 71
scrolling
in web applications, 61
security
basic measures for the web, 53
HP OpenView Launcher, 45
user roles, 53
security, in web applications, 53
selecction
383
Index
384
labels, 296
placement, 296
sliders
when to use, 296
spin box
default action, 295
default value, 295
guidelines, 293, 295
labels, 294
placement, 294
when to use
, 293
split windows, 98
menus, 99
scope pane, 98
specifying content, 98, 99
toolbars, 99
status
compound presentation, 213,
248
conflicts between applications,
247
in task presentation managers,
83
reporting by object, 247
reporting by symbol, 248
status area, 74
status bar, 167
status colors, 245
status source, 247, 248
setting, 247
submap window
geometry, 215
overlay, 217
submaps
in NNM, 211
independent, 182
persistent, 212
shared, 212
shared vs. exclusive, 211
transient, 212
symbol alerts, 249
guidelines, 250
removing, 251
severity levels, 250
text annotation, 254
types, 251
user interaction, 251
when to ue, 250
symbol design
creating new connection
classes, 196
creating new object classes,
195
graphical cues for classes, 194
guidelines, 190
using existing classes, 190
symbols, 171, 206, 255, 259, 271
annotating, 254
assigning to connections, 187
assigning to objects, 185, 186
changing type, 209
classes, 190
connection, 207, 261
connection line style, 207
connection subclasses, 207
connection thickness, 208
creating new subclasses, 204
flashing, 256
for representing objects, 171
highlighting, 255
new subclasses, 204
see also graphics, 171
software utilities, 188
subclasses, 197
symbol types, 185
to represent actions, 188
transparent, 257
user addition of, 210
user modification, 209
using existing graphics, 197
T
tab categories
for web launcher, 40
Index
Index
tab controls
bottom placement, 316
guidelines, 314318
horizontal alignment, 316
labels, 315
multiple rows of tabs, 317
top placement, 316
vertical alignment, 316
visual cues, 318
when to use, 80, 315
table
default action, 313
default values, 314
editing entries, 310
filter, 311
guidelines, 307314
input focus, 310
keyboard navigation, 312
labels, 309
placement, 309
selection, 312
sequencing, 311
when to use, 308
tables
in web applications, 65
tabular presentation format, 153
for objects, 154
task based approach, 21
task presentation managers, 79
related tasks, 84
results pane, 80
scope pane, 80
status, 83
use of navigation tabs, 82, 84
use of push buttons, 81
when to use, 80
task support, 84
text annotation, 254
user interaction, 254
with symbol alerts, 254
text box
data entry, 289
default action, 291
Index
U
user approaches, 21
user guided approach, 22
user roles
guidelines for setting, 47
in HP OpenView Launcher, 46
V
Vision
for HP OpenView applications,
20
visual cues
controls, 270
filling connection symbols, 261
flashing symbols, 256
for drag and drop, 234
for recursive selection, 229
general, 243
highlighting, 255
in graphics, 198
in menus, 123
in navigation tabs, 162
in split windows, 99
in tab controls, 318
in the scope pane, 143
push button, 281
status colors, 245
symbol alerts, 249
transparent symbols, 257
using to report object
conditions, 244
using vs. event, 244
W
web applications, 37
colors, 55
context area, 68
control frame, 74
fonts, 60
forms, 66
frames, 63, 65
general guidelines, 54
385
Index
graphics, 60
HTML, 65
images, 60
in web browser, 49
launching, 39
link color, 55
navigation, 49, 62
progress indicator, 51
results pane, 72
scoping pane, 71
scrolling, 61
security, 53
status frame, 74
tables, 65
title bar, 67
toolbar, 68
type of browser window, 51
updating information, 63
use of browser controls, 52
use of named windows, 54
use of patterns, 59
window components, 67
web browser, 49
type of window, 51
web launcher
concepts, 24
description, 39
object tab, 42
registration guidelines, 41
security, 45
session information, 47
tab categories, 40
task tab, 43
tools tab, 43
user roles, 46
web launchrs
graphics, 45
window components
identifying, 105
windows, 92
creating new, 101
multiple pane, 96
resizing, 268
386
Index