Developing a DSL Graphical Notation - Eclipse Modeling Project: A Domain-Specific Language Toolkit - page 141

Element Property Value

Typed selection filter Generated Types abstractNavigatorItem

Types in selection org.eclipse.requirements.Requirement,

org.eclipse.requirements.diagram.edit.parts.
RequirementEditPart

When we regenerate our diagram, we find the following additions to the
plugin.xml file and the default generated property section class. Note that if
you marked the propertySections element as generated="false" during
the steps to combine editors, you don't see the new property section. To regen-
erate in this case, set the value to true after backing up the changes and merge
manually afterward.

<extension
point="org.eclipse.ui.views.properties.tabbed.propertyContributor">
. . .
<propertyCategory category="visual"/>
<propertyCategory category="extra"/>
</propertyContributor>
</extension>

<extension point="org.eclipse.ui.views.properties.tabbed.propertyTabs">
. . .
<propertyTab
category="domain"
id="property.tab.domain"
label="%tab.domain"/>
<propertyTab
category="extra"
id="property.tab.description"
label="%tab.description"/>
</propertyTabs>
</extension>

<extension
point="org.eclipse.ui.views.properties.tabbed.propertySections">
<?gmfgen generated=" false "?>
. . .
<propertySection
id="property.section.description"
tab="property.tab.description"
class="org.eclipse.requirements.diagram.sheet.
RequirementDescriptionPropertySection">
<input type="org.eclipse.requirements.Requirement"/>
<input type="org.eclipse.requirements.diagram.edit.parts.
RequirementEditPart"/>
<input type="org.eclipse.requirements.diagram.navigator.
RequirementsAbstractNavigatorItem"/>