Chat now with support
Chat mit Support

Foglight 7.1.0 - Web Component Guide

Introducing the Web Component Framework The Web Component Framework Configuring Views and Context Queries Functions Bindings Additional Components

Icons

The Icons choice allows you to configure how graphics render in the Web Component Framework. In a view definition, an icon can be referenced directly by using an Icon binding and then setting an Icon Renderer to specify the desired size. In the Types tab, an icon can be mapped to a data type. In a view definition, selecting data of that type and specifying an Icon Renderer causes the data to display as the mapped icon.

Icons collect differently-sized (but similar in appearance) images under a single name. Images can be specified for the following sizes:

•
Extra small (8x8 pixels, or 9x9, depending on the image)
•
Small (11x11 pixels)
•
Medium (16x16 pixels)
•
Large (32x32 pixels)
•
Extra large (64x64 pixels)
•
Huge (128x128 pixels)
•
Scalable (any size)
 
* 
NOTE: Each size should have its own image that has been created with the appropriate number of pixels. The icons are then uploaded from the Files section.

Associations

Associations provide a mechanism to organize references into entities. A typical association contains a label (a renderable artifact), one or more tags for organization, and a reference to an entity, frequently a view. Different types of associations include properties that are specific to their purpose.

The following types of associations are available:

•
Tab Associations
•
Question Associations
•
Category Associations
•
Domain Associations
•
Message Associations
•
Customizable Associations
•
Hierarchy Associations
•
Alarm Associations
•
Activity Associations
•
Action Associations
•
Node Associations
•
Edge Associations

Tab Associations

Tabs supply views to the Tab Manager component. The reference contained by a tab association is a view, displayed by the Tab Manager component when the tab is selected.

Tab Associations are configured and managed like view components, except that they have no flow (and therefore no generated context). The purposes of a tab association include:

•
Providing a label (title) for the referenced view that can be displayed without the view being loaded
•
Permitting more control over the selection of dynamically-loaded tabs
•
Allowing context re-mapping between the Tab Manager and the referenced view (which is normally not possible for views which are dynamically added to a container)

A tab association contains the following elements:

•
Label and description, used to display the tab
•
View, displayed when the tab is selected
•
A set of tags, used by the Tab Manager component to find the applicable tabs to display
•
Priority property, used to order the tabs
•
Display property, used by the Tab Manager to determine if the tab is visible or not.

Question Associations

Questions are used by the question viewer and mini-viewer components. The label-type property is Question which contains the text of the question to display, and the Answer View contains the answer to that question.

Questions belong to a domain (see Domain Associations), that broadly filters the set of all questions to those appropriate for a particular viewer instance with a corresponding Domain property set. Each question has one or more categories, that control grouping and are used for navigation. In addition, a question can have an associated Report View, used if the question is added to a report.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen