Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Riena/Toolbox"
(→AssemblyEditor) |
(→AssemblyEditor) |
||
| Line 3: | Line 3: | ||
The Riena assembly in short is a set of extensions that define the navigation structure of Riena applications. Assemblies define the way the [http://wiki.eclipse.org/Riena/Navigation navigationtree] of a Riena-Application looks like. | The Riena assembly in short is a set of extensions that define the navigation structure of Riena applications. Assemblies define the way the [http://wiki.eclipse.org/Riena/Navigation navigationtree] of a Riena-Application looks like. | ||
| − | The AssemblyEditor is an improved treebased editor like the PDE extensionpoint editor, that offers much more comfort when editing assemblies. | + | The AssemblyEditor is an improved treebased editor like the PDE extensionpoint editor, that offers much more comfort when editing assemblies. Besides having a richer editor for the navigationtree the AssemblyEditor can generate Javacode like Views/Controller from a template. So instead of creating a SubModuleView, registering it under the extensionpoint org.eclipse.ui.views, you can just let the AssemblyEditor do all the tedious work for you. |
| + | |||
| + | Furthermore the AssemblyEditor can generate missing getRidget-calls in the SubModuleController for the corresponding Widgets. We support a roundtrip engineering at this point, so you can edit your SubModuleController like you are used to and let the AssemblyEditor update your missing getRidget-calls. | ||
[[Image:AssemblyEditor_1.png]] | [[Image:AssemblyEditor_1.png]] | ||
=Previewer= | =Previewer= | ||
Revision as of 09:15, 15 March 2011
Wizards
AssemblyEditor
The Riena assembly in short is a set of extensions that define the navigation structure of Riena applications. Assemblies define the way the navigationtree of a Riena-Application looks like.
The AssemblyEditor is an improved treebased editor like the PDE extensionpoint editor, that offers much more comfort when editing assemblies. Besides having a richer editor for the navigationtree the AssemblyEditor can generate Javacode like Views/Controller from a template. So instead of creating a SubModuleView, registering it under the extensionpoint org.eclipse.ui.views, you can just let the AssemblyEditor do all the tedious work for you.
Furthermore the AssemblyEditor can generate missing getRidget-calls in the SubModuleController for the corresponding Widgets. We support a roundtrip engineering at this point, so you can edit your SubModuleController like you are used to and let the AssemblyEditor update your missing getRidget-calls.
