Difference between revisions of "Class Browser"
(→Node Texts) |
|||
| Line 15: | Line 15: | ||
====Tooltips==== | ====Tooltips==== | ||
| − | Hovering with the mouse over a tree node will bring up a Tooltip-Text, showing you the system type of the respective object and if it is currently | + | Hovering with the mouse over a tree node will bring up a Tooltip-Text, showing you the system type of the respective object and if it is currently in [[Live mode|Live-]] or in [[Sandbox mode|Sandbox]]-mode. Depending on the actual type of the object, there will be additional information presented in the Tooltip. |
====Node Texts==== | ====Node Texts==== | ||
| Line 29: | Line 29: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| − | ! Menu !! Purpose | + | ! Menu !! Object Type !! Purpose |
|- align="left" | |- align="left" | ||
| − | | | + | | Derive new object || MetaClass || Creates a new derivate of the context MetaClass |
|- align="left" | |- align="left" | ||
| − | | | + | | Navigate To || All || Opens the navigation menu |
|- align="left" | |- align="left" | ||
| − | | Delete || Deletes the object from cache. It will only be removed from the database after a Save | + | | Save || All || Saves changes on the object to the database |
| + | |- align="left" | ||
| + | | Delete || All || Deletes the object from cache. It will only be removed from the database after a Save | ||
| + | |- align="left" | ||
| + | | Released || MetaClass || Transfers the MetaClass into [[Live mode|Live-]] (=Released) or back into [[Sandbox mode|Sandbox]]-mode | ||
|} | |} | ||
| + | |||
| + | ===Drag & Drop=== | ||
| + | The ClassBrowser is a source for Drag&Drop operations, any object (with the exception of Namespaces) can be dragged from here. | ||
==Toolbar== | ==Toolbar== | ||
| Line 52: | Line 59: | ||
===Hierarchical=== | ===Hierarchical=== | ||
| − | In this | + | In this view mode, the [[Derivate|Derivates]] relation from each [[MetaClass]] deriving directly or indirectly from [[UBIK Metaclasses for Data Modelling#BaseClass|BaseClass]] will be evaluated. It is also the Style where new MetaClasses should be created by deriving from exiting ones. |
===Inheritance=== | ===Inheritance=== | ||
| − | In this | + | In this view mode, the [[Inheritance]] relation of all MetaClasses will be evaluated. So expanding a node will display its inheritance owner below it, which implies that in this view there can only be exactly one node below another. |
===Content=== | ===Content=== | ||
| − | In this | + | In this view mode, the [[Instances|Instances]] of all MetaClasses will be evaluated. |
==Other functionality== | ==Other functionality== | ||
[[Category:UBIK Studio Controls]] | [[Category:UBIK Studio Controls]] | ||
Revision as of 10:21, 6 February 2013
Contents
Purpose
The Class Browser is designed to display and edit UBIK® objects in a hierarchical manner. It is also meant to be the superior of all other controls and the only one where at least one instance of it is actually mandatory in a UBIK® Studio session. So it can be considered as the root of object manipulation in UBIK®.
In addition, it makes use of Namespaces and uses them for structuring the displayed objects even further.
Basics
Appearance
Icons
Depending on the current View Style, the control display different types of UBIK® classes. Each major class type is associated with a unique icon, in order to provide a visual distinction of the class types. However, these icons can be replaced by more specific ones during the customization process, which means that it is not a reliable indicator if an object is of a certain type.
The coloring of an icon indicates another object status: if the icon appears grey instead of its regular coloring, the respective object is considered as a system object.
A blue triangle in the upper left corner of an icon indicates that the object is an instance of another object in the same view.
Tooltips
Hovering with the mouse over a tree node will bring up a Tooltip-Text, showing you the system type of the respective object and if it is currently in Live- or in Sandbox-mode. Depending on the actual type of the object, there will be additional information presented in the Tooltip.
Node Texts
The nodes will always display the string representation of the respective object, which is by default
- Name Description for MetaClasses
- Description (Name) for Content objects
However, as this is something that can be customized, the nodes might display something different.
Clicking a node with the right mouse button will bring up a standard context menu for each node, except Namespaces. Depending on the View Style there will be different options, however, all nodes will at least show the following menu items:
| Menu | Object Type | Purpose |
|---|---|---|
| Derive new object | MetaClass | Creates a new derivate of the context MetaClass |
| Navigate To | All | Opens the navigation menu |
| Save | All | Saves changes on the object to the database |
| Delete | All | Deletes the object from cache. It will only be removed from the database after a Save |
| Released | MetaClass | Transfers the MetaClass into Live- (=Released) or back into Sandbox-mode |
Drag & Drop
The ClassBrowser is a source for Drag&Drop operations, any object (with the exception of Namespaces) can be dragged from here.
Toolbar
| Control | Purpose |
|---|---|
| View Style | Indicates or changes the View Style of the control; changing it will result in reloading of the control |
| Search | Allows to perform a (visual) search through the labels of the tree nodes; found objects will be highlighted accordingly |
View Styles
The Class Browser has three different View Styles, each of the providing different views and functionality.
Hierarchical
In this view mode, the Derivates relation from each MetaClass deriving directly or indirectly from BaseClass will be evaluated. It is also the Style where new MetaClasses should be created by deriving from exiting ones.
Inheritance
In this view mode, the Inheritance relation of all MetaClasses will be evaluated. So expanding a node will display its inheritance owner below it, which implies that in this view there can only be exactly one node below another.
Content
In this view mode, the Instances of all MetaClasses will be evaluated.
