Extending the Structure Editor: Difference between revisions
From Event-B
Jump to navigationJump to search
imported>Jrloria No edit summary |
imported>Jrloria No edit summary |
||
| Line 1: | Line 1: | ||
The "edit" view is mainly a tree with elements as nodes and attributes as value for nodes. | |||
The Extension Point is org.eventb.ui.editorItems | |||
So, each new internal element should be map to a "element" (=configuration of the display). After elements should be placed in the tree with a childRelation (=where the element appear) and each attribute of the internal element should be placed with a attributeRelation (=where the attribut appear) | |||
=== Adding a New Element === | === Adding a New Element === | ||
Revision as of 09:21, 18 May 2010
The "edit" view is mainly a tree with elements as nodes and attributes as value for nodes. The Extension Point is org.eventb.ui.editorItems So, each new internal element should be map to a "element" (=configuration of the display). After elements should be placed in the tree with a childRelation (=where the element appear) and each attribute of the internal element should be placed with a attributeRelation (=where the attribut appear)
Adding a New Element
Adding a New Attribute
The extension point org.rodinp.core.attributeTypes is used to declare a new displaying/editing a new attribute in the Structure Editor. There are two steps for doing this: first, How the attribute is going to be displayed/edited and second, the relationship between the attribute and internal elements.
