Icons can be used to assign symbols to elements and actions. This helps in the differentiation of the displayed types at run time, or for orientation in context menus, table views, tree views and so forth.
Modeled icons can appear, for example, in the following places at run time:
A function package provider has the possibility to support directly the icons for elements which belong to a linked element type.
Example: The Eclipse function package supports all icons which are used for Eclipse resources (projects, folders, and files), so it is not necessary to create those icons in the AWM model editor.
A function package provider has the possibility to support additional icons which can be used in the AWM model editor. Those icons are typically used to add icons to actions.
Icons are modeled by being defined once and then referenced in the Element Type or Action Descriptor.
There are two available icon types:
Generic icon type which must have a unique ID and a reference to one of the pre-defined icon images, which can be selected through the “predefined” attribute of the icon. Predefined icons with names starting with “Action” are shown in grey if a modelled action cannot be executed due to an action-enabled condition.
|ID *||ID *||The ID of the icon.|
|Predefined||Selection||This attribute is used to select an icon. The selected icon image is visible in the model editor, once the attribute value has been set.|
Icon defined by a function package. See Extending the AWM Meta Model for more information.
If a function package containing icons is added to a model, desired icons can simply be created by selecting them under.
Function package icons can have separate icon images for disabled actions, which are automatically used by AWM if the icon is associated to an action which is disabled due to an enabled condition.