NAVAIR INSTRUCTION 4120.11 From: Commander, Naval Air ...

NAVAIRINST 4120.11
function when selected. In a drop-down menu, this appears next
to the function selected. There may be several levels of
cascading menus. Functions that are not active during any
rendering shall be presented as disabled (grayed out). The main
menu bar is mandatory and shall not be toggled off. The bar
shall remain accessible by persistent visible indication (e.g.,
the guide post).
5.14 . Project specific bar. The project specific bar can be used
if additional functions are required. Consideration should be
given for placement of functions on the project specific bar
with respect to main menu bar functions to minimize potential
for making incorrect selections (for example, the project
specific functions may be oriented so that the functions are
right justified). The project specific bar is optional and may
be toggled on and off. Functions that are not active during any
rendering should be presented as disabled (grayed out).
Cascading menus may appear as a child of a function when
selected. In a drop-down menu, this appears next to the
function selected. There may be several levels of cascading
menus.
5.15 . Main content area. The main content area contains the text
and graphics of the IETM, specifically excluding the table of
contents panel, guide post, classification bar, navigation panel
and status bar.
5.16 . Status bar. The status bar should be a horizontal bar
located at the bottom of the inner shell. The status bar should
contain status information including status indicators and icons
for active (persistent) warnings, cautions, and notes. The
status bar may be toggled on and off when there are no
persistent alert icons. The status bar should not be toggled
off when persistent alert icons are displayed.
5.17 . Screen sizes. Proper planning for the size and resolutions
of various devices up front in the planning stages makes lifecycle
sense as the presentation technology is always undergoing
change (e.g., terminals, desktops, laptops, personal digital
assistance devices, etc).
6. MAINTAINING A COMMON LOOK-AND-FEEL AMONG DIFFERING IETMs.
6.1 . Overview. While the use of the common browser does
standardize many of the user-interaction features, it is very
likely that a custom component may contain its own set of unique
user-interaction features layered under the higher-level browser
toolbars. These features often conform to a proprietary lookand-feel
dictated by the COTS product being employed. However,
the need for a procurement-guidance document that can be
Enclosure (4) 18