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 "EEF/User Guide/Custom Element Editor"
(→Need of new widget ?) |
(→Modifying the generated code) |
||
Line 26: | Line 26: | ||
== Modifying the generated code == | == Modifying the generated code == | ||
+ | |||
+ | By using CustomElementEditor, EEF generates user code areas in three classes. We need to complete these classe to includes our own widget and to bind it with the EMF model. The three classes to modify are : | ||
+ | * the PropertiesEditionPartForm : '''XXXPropertiesEditionPartForm''' | ||
+ | * the PropertiesEditionPartImpl : '''XXXPropertiesEditionPartImpl''' | ||
+ | * the PropertiesEditionComponent : '''XXXPropertiesEditionComponent''' | ||
+ | |||
+ | === Modifiying the PropertiesEditionPartForm === | ||
+ | |||
+ | === Modifiying the PropertiesEditionPartImpl === | ||
+ | |||
+ | === Modifiying the PropertiesEditionComponent === |
Revision as of 09:26, 5 January 2012
Contents
Need of new widget ?
EEF generators offer a set of widget to build EMF editing forms. Sometime other widget needs appear to create more efficient GUIs. In this case, EEF users can employ CustomElementEditor to generate user code areas inside the EEF properties code.
Let's start this sample with this sample Ecore model :
By following the first generation tutorial, EEF generates theses forms :
Now suppose we want to use a spinner instead of a Text for the age entry. Spinners aren't yet available in the EEF generation. We can, in this case use a CustomElementEditor.
CustomElementEditor in the EEF models
The first step is to replace the ElementEditor generated by the EEF Initializer with a CustomElementEditor. This must be done in the View associated to our EClass Person, the "Person" View.
The removed ElementEditor was defined as the view of the "age" PropertiesEditionElement of the "Person" PropertiesEditionComponent. We need to define our CustomElementEditor as the new "age" PropertiesEditionElement view.
These changes made, we can regenerate the EEF code.
Modifying the generated code
By using CustomElementEditor, EEF generates user code areas in three classes. We need to complete these classe to includes our own widget and to bind it with the EMF model. The three classes to modify are :
- the PropertiesEditionPartForm : XXXPropertiesEditionPartForm
- the PropertiesEditionPartImpl : XXXPropertiesEditionPartImpl
- the PropertiesEditionComponent : XXXPropertiesEditionComponent