Difference between revisions of "Extending the Rodin Database"

From Event-B
Jump to navigationJump to search
imported>Son
imported>Son
Line 15: Line 15:
 
       </attributeType>
 
       </attributeType>
 
   </extension>
 
   </extension>
The attribute has an id (which should be always unique) which also contain the project name, i.e. <code>org.eventb.developer.examples.stringAttr</code>. The name of the attribute is a string that could be externalised to be used for displaying to the users in the future.
+
The attribute has an ID (which should be always unique) which also contain the project name, i.e. <code>org.eventb.developer.examples.stringAttr</code>.  This unique ID will be used for access the value corresponding to this attribute of an element later. The name of the attribute is a string that could be externalised to be used for displaying to the users in the future. There are five different attribute kinds: ''boolean'', ''handle'', ''integer'', ''long'', ''string''

Revision as of 16:17, 24 March 2010

Adding a New Element

Adding a New Attribute to Existing Elements

The extension point org.rodinp.core.attributeTypes to declare a new attribute.

In the example below, we assume that the extensions are developed within a plug-in project with name org.eventb.developer.examples

The following extension declares a new string attribute.

<extension
        point="org.rodinp.core.attributeTypes">
     <attributeType
           id="stringAttr"
           kind="string"
           name="%eventBStringAttribute">
     </attributeType>
 </extension>

The attribute has an ID (which should be always unique) which also contain the project name, i.e. org.eventb.developer.examples.stringAttr. This unique ID will be used for access the value corresponding to this attribute of an element later. The name of the attribute is a string that could be externalised to be used for displaying to the users in the future. There are five different attribute kinds: boolean, handle, integer, long, string