Java Reference
In-Depth Information
implementation of a generated diagram, you can do so by overriding or aug-
menting the models and Xpand templates. Furthermore, Bugzilla has an out-
standing request to enhance the generator to provide for diagram extensions.
Two approaches are considered for this extension:
Begin with the existing diagram definition models and provide extensions
that, when regenerated, produce a new diagram that extends the original
❍
Use a set of extension tooling models that target runtime extension-points
opened in the diagram that the Toolsmith can extend
❍
10.3.1 Extension-Points
The GMF runtime provides 27 extension-points for contribution in your dia-
gram, while the tooling provides another 2 for its dashboard and validation. Of
course, not all need to be used. The following sections provide information on
each extension-point, most of which are found in the extension-points Reference
section of the GMF help or can be viewed using PDE's Show extension-point
Description feature. I provide this here for convenience, plus it contains addi-
tional examples, comments, and usage tips.
Note that every extension-point declaration includes an
ATTLIST
that is the
same, including point, ID, and name attributes. These details are included in each
schema description and are not reproduced here, to save space. Only the exten-
sion
ELEMENT
declaration is provided.
<!ELEMENT extension (elements)>
<!ATTLIST extension
point CDATA #REQUIRED
id CDATA #IMPLIED
name CDATA #IMPLIED>
point
—The identifier of the extension-point—for example,
org.eclipse.
gmf.runtime.common.core.logListeners
.
id
—The identifier of the extension—for example, logListeners.
name
—The name of the extension—for example, %ext.logListeners. (Note
that
%
-prefixed Strings indicate localized Strings found in corresponding proper-
ties files.)
Additionally, several elements are used in multiple extension-point defini-
tions. I list them here, to avoid duplication throughout this section.
Search WWH ::
Custom Search