Java Reference
In-Depth Information
This element specifies a
pathmap
variable to be registered with the runtime.
name
—The variable name.
plugin
—The plug-in that contains the path, if different from the plug-in
that defines the extension.
path
—The path, relative to the plug-in location (as indicated by the plug-in
attribute, if specified, or the current plug-in, if not).
Examples:
This example illustrates the definition of a
pathmap
to locate libraries in the
UML2 project. Using this
pathmap
, you can use URIs such as the following to
reference UML2 library resources:
pathmap://UML2_LIBRARIES/Ecore.
library.uml2
.
<extension
id="UML2Libraries"
name="UML2 Libraries"
point="org.eclipse.gmf.runtime.emf.core.Pathmaps">
<pathmap
name="UML2_LIBRARIES"
plugin="org.eclipse.uml2.resources"
path="libraries">
</pathmap>
</extension>
API information:
This extension-point has no associated API.
Notes:
Diagrams generated using the GMF tooling do not currently use this
extension-point.
With the basics of the notation model and services under our belt, let's bring it
together and compare how GMF's runtime differs from what we learned about
GEF in Chapter 9. We look at element creation because it is the most funda-
mental use case and nicely illustrates how GMF differs from GEF. You might
want to compare Figure 10-47 and the following description of GMF element
creation with that of GEF element creation covered in Section 9.2.6,
“Interactions.”
This initial sequence for element creation is similar to GEF, with the major
difference being GMF's use of a
CreationEditPolicy
that uses a compound
Search WWH ::
Custom Search