iView Containers - TraysIntroduction | What is a Tray? | Tray Functionality | Tray Types IntroductionAn iView consists of two parts: The actual application written by a development team and a framework or container encapsulating the application. This framework is implemented through a design element called tray which serves as a container for iViews. While the application implements most of the functionality and the behavior experienced by the user, the tray delivers interfaces to common functions used by nearly all iViews. These functions comprise an hide/show mechanism and the ability to personalize an iView. The tray is responsible for displaying the appropriate user interface elements, while the application delivers the content via standardized interfaces.
What is a Tray?A tray is part of the portal framework. It serves exclusively as a container for iViews. A tray consists of a header bar and a content area (see figure 1). A status area may be offered in the future.
Figure 1: The iView tray (shown in "simple" tray design) The header bar (see figure 1) contains the iView title (left) and small icons (right) for accessing standard tray functionality. See Tray Functionality below for the functions. Trays are available in four different designs (see figure 2). The different designs are distinguished by the color of the content area, and by whether the content area has a border or not. For details see Tray Types below.
Figure 2: A portal page showing all four tray designs
Tray FunctionalityThe tray provides the following functions (see figure 1 above and 3 below).
Figure 3: The tray functions Personalize (Edit)The edit icon ( Note: Currently, the personalization of an iView has to be handled by the iView itself. There is no general personalization interface available. See Personalizing iViews for preliminary proposals for personalization dialogs. Toggle Open/Close (Restore/Collapse)The tray has a toggle button that allows users to open (collapse) and
close (restore) an iView. An open iView's header shows the "close"
icon ( Expand (Open in a New Window)The expand icon ( RemoveIf the user clicks the "remove" icon ( RefreshThe "refresh" icon ( Complex RefreshSome iViews will contain data that is changing over time. Examples are stock quotes or inbox items. Depending on the character of the iView, knowing exactly how old or recent the displayed information is can be crucial to overall usability of the application. Besides knowing about the"age" of a piece of information it will in some cases be necessary to update the content of an iView as required. The intervals for the updating or "refresh" procedure can vary from once a day to every minute, from automatic to manual refresh. Setting this parameter will be handled via a Refresh button or personalized settings. Note: Until now, there is no solution for automatically providing the refresh button in the tray. It must be placed within the iView manually and should be the rightmost button of the row which also contains iView's emphasized button (if there is any), i.e. usually at the bottom of the iView. Provide a hint on how old the information displayed in the iView is - don't just enter the last screen refresh date, but when the last query was conducted (if appropriate). Further information: For information on messages in iViews see Messages; for error handling, error prevention and user support see Help and User Support.
Tray TypesCurrently (ERP 5.0), there are four tray types available:
These tray types differ from each other on the following three dimensions:
Having a variety of tray designs at your disposal reduces the danger that a portal page has a monotonous visual appearance and helps users in differentiating iViews from each another. Each of the trays comes with a name referring to its proposed content; we also provide the value that has to be assigned to the attribute design. The trays are presented here in order of their importance. The Form TrayThe form tray (design = FORM) has a colored header bar, no outside border, and a light colored background color for the content. Use it whenever an iView's content consists of form elements, such as an entry field, a dropdown list box, checkboxes, or radio buttons: White input fields can be clearly distinguished from the slightly colored background of this tray type. Grouping of the elements sets them apart from the colored background.
Figure 3: The form tray The Border TrayThe border tray (design = BORDER) has a colored header bar, an outside border, and no background color for the content. A collection of different elements is hardly recognized as a group. If such elements belong together they need a frame. Use this design to group such element collections and still retain a decent grouping.
Figure 4: The border tray
|