Adding non-standard elements in a page
The previous exercise showed you that you could include a list (ListView) in a page by browsing a MetaAssociationEnd defined on a MetaClass of the object.
The main elements you can feature in a Properties page are listed below.
ListView: view as list
A ListView enables display of a list obtained by browsing a MetaAssociationEnd or a Query from an object in the Properties page. Queries that can be used in this context are either queries without parameters, or queries that have an occurrence as their only parameter.
You can:
• configure the list of columns displayed (which are generally attributes of browsed objects), as well as the list toolbar.
• create a list displaying several distinct collections, by selecting the active collection from the toolbar.
TreeView: view as tree
A treeView enables display of a tree, built from a list of MetaAssociationEnds and Selectors, the root of which is the object in the Properties page. This list can be deduced from an _Operator.
You can:
• define if a path can be of several levels or a single level.
• display folders or not.
• configure the tree toolbar.
Example: the following element displays the default navigation tree of an object. Here, Navigate is the _operator used to define the path.
Tree=Item(~laCnbKSWt000[Navigate]),Control(TreeView),Param(IsDeep)
Viewer: HTML formatter display
You can include an HTML formatter in a Properties page. This formatter will be generated from the object in the Properties page. In this way you can display any content in a Properties page, on condition that it is not intended for update.
You can trigger an action in this HTML document when you execute ‘Apply' on the Properties sheet.
HelpComment: help comment display
You can include help text in a Properties page. This text can be text from system data or from modeled data.
SubPage: page in page display
You can display a Properties page in another page, for example to reuse an implementation which can be defined in a generic page.