Difference between revisions of "View Test Environment"
| Line 14: | Line 14: | ||
[[File:UI_ViewTest_NewFile.png|thumb|right|220px]] | [[File:UI_ViewTest_NewFile.png|thumb|right|220px]] | ||
Right click on a node to bring up it's context menu. If applicable, it will bring up a context menu allowing you to create new objects according to the view definition. | Right click on a node to bring up it's context menu. If applicable, it will bring up a context menu allowing you to create new objects according to the view definition. | ||
| + | |||
| + | |||
| + | |||
===Editing=== | ===Editing=== | ||
Selecting an object in the tree will load it's properties into an [[Object Editor]] control in the right area of the View Test window. | Selecting an object in the tree will load it's properties into an [[Object Editor]] control in the right area of the View Test window. | ||
Revision as of 06:51, 14 May 2013
As the name already states, the View Test Environment enables you to test Views, without deploying them via Application Context Management. So it can and shall be used to perform a dry-run of created or modified views, e.g. to check the resulting objects of the different levels. But it can also be used to edit data in a hierarchical way. It not only allows the creation of objects via a context menu according to the view definition, but also the editing of properties of all objects once the changes were released with the UBIK® Compiler.
 | This control will exclusively display properties that were already compiled into the customizing assembly! |
Basics
Toolbar
Exploring
Right click on a node to bring up it's context menu. If applicable, it will bring up a context menu allowing you to create new objects according to the view definition.
Editing
Selecting an object in the tree will load it's properties into an Object Editor control in the right area of the View Test window.
