SeeView Manual

SeeView Programming
HP NonStop SeeView Manual—526355-004
6-4
Develop a Firm Understanding of Utility Command
Structure
in command syntax not only helps with the design of an interface but also greatly
simplifies the implementation, usability, and readability of the script.
Develop a Firm Understanding of Utility Command Structure
Study the manuals and reference summaries. Your goal is to gain a firm understanding
of the command structure and limitations of the utility. For example, certain utilities
have the same consistent command structure for each command:
command [object-type] [object] [,attribute].[,attribute]
However, for other utilities, command structure can be inconsistent and can depend on
the type of object or subsystem used.
When you are confident of your ability to write the script and to understand the syntax
of the utility for which you are designing the interface, consult an experienced SeeView
user (if available) to discuss the presentation techniques. When talking with this
experienced user, discuss the design you are considering. You might discover a new
set of ideas for displaying information, basic operation, desired improvements, and the
most commonly used commands.
Define What You Want Your Script to Accomplish
Before you proceed, you must clearly understand what you want your script to achieve,
whether it is simplifying an interface, improving the interface by providing a higher-level
of integration, or adding new functionality.
Establish Menu and Window Contents
Start thinking about the contents of menus and windows, but do not be concerned
about their sizes, locations, or types. Create your menus in a top-down format, moving
from the general to the specific by listing the contents of the first menu and breaking it
down. You might find an outline helpful.
Start with the main menu. For example, the main menu could be a division of the major
commands or functions, or the main menu could be a division of subsystems. If only
some of the commands reference all subsystems, you should organize the main menu
by subsystem, because each subsystem cannot be uniformly referenced by each
command.
The syntax of commands that can be executed for all subsystems is usually varied, so
dividing subsystems into individual parts with their own commands simplifies the
structure. As you continue to build your menus, they may become very detailed. Keep
in mind that you should probably change the menus as you continue.