Extending the Rodin Database: Difference between revisions
From Event-B
Jump to navigationJump to search
imported>Son |
imported>Son |
||
Line 3: | Line 3: | ||
== Adding a New Attribute to Existing Elements == | == Adding a New Attribute to Existing Elements == | ||
The extension point <code>org.rodinp.core.attributeTypes</code> to declare a new attribute. | The extension point <code>org.rodinp.core.attributeTypes</code> 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''' | |||
<extension | <extension | ||
point="org.rodinp.core.attributeTypes"> | point="org.rodinp.core.attributeTypes"> | ||
<attributeType | <attributeType | ||
id=" | id="probai" | ||
kind="string" | kind="string" | ||
name="%eventBConfigurationAttribute"> | name="%eventBConfigurationAttribute"> |
Revision as of 15:58, 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
<extension point="org.rodinp.core.attributeTypes"> <attributeType id="probai" kind="string" name="%eventBConfigurationAttribute"> </attributeType> </extension>
In order to access an attribute of an internal element