Eclipse Development using the Graphical Editing Framework and the Eclipse Modeling Framework
Anna Gerber, Bill Moore, David Dean, Gunnar Wagenknecht, Philippe Vanderheyden
Format: PDF / Kindle (mobi) / ePub
Eclipse Development using the Graphical Editing Framework and the Eclipse Modelling Framework is written for developers who use the Eclipse SDK to develop plug-in code. This IBM Redbooks publication is intended for a technical readership and for developers who already have good knowledge and experience in Eclipse plug-in development.
In this book, we examine two frameworks that are developed by the Eclipse Tools Project for use with the Eclipse Platform: the Graphical Editing Framework (GEF), and the Eclipse Modeling Framework (EMF). We cover both the Graphical Editing Framework and the Eclipse Modeling Framework, but these frameworks can be used separately, and there is no dependency between them.
This book provides a high level introduction to these frameworks so that Eclipse plug-in developers can consider whether the frameworks will be useful for the requirements of their particular development environment. Next, tips and techniques are provided for writing code that uses GEF and EMF. Also, a detailed example is developed to illustrate a GEF editor that uses an EMF model.
Not added directly to the interface, instead, we have to define an accessor for it. Code generation completes the interface by defining the setter and provides the implementation of both the setter and the getter. Example 1-2 shows the x attribute @model tag. Example 1-2 The x attribute @model tag /** * @model default="0" */ int getX(); Adding associations For each reference, we have to define: The type of object it gives access to. If it is a containment reference. The name of the second.
Source 1 Edges 0..* Inputs 1..* InputPort Target 1 Edges 0..* Edge Edges 0..* Figure 2-3 Model of Workflow with additional common supertype Working with packages EPackages are used to collect EClasses and EDataTypes together in much the same way that packages are used in Java. In this section, we discuss models that span multiple packages. Typically packages are used to group related concepts into reusable modules. When creating an editor for a model, it is often necessary to store.
Use the setName() method on the XMLInfoImpl to customize the name of the element or attribute tag used in the XML, and setTargetNamespace() to set the namespace for that element or attribute. Use setXMLRepresentation() to specify whether the object is represented as an ELEMENT, ATTRIBUTE or CONTENT. Specifying CONTENT results in the value of object being contained directly by its parent. For example, we might use CONTENT to represent the condition attribute of a ConditionalOutputPort so that.
Information is the template drag and drop palette demonstrated in the Logic example application provided by GEF. Our sample application will also provide an introduction into implementing drag and drop. Chapter 4. GEF examples 143 4.2.2 Palette: Implementing a sticky tool preference The default behavior for GEF tools is to unload a tool after it is used once. This causes the EditDomain’s default tool, which is typically the SelectionTool, to be reactivated. This behavior is desirable for some.
Result. Chapter 1. Introduction to EMF 11 1.3.4 Modeling using the EclipseUML plug-in During our simple model creation, we iterate several times to achieve what we think is a good design. The graphical facilities of the EclipseUML plug-in are a great help during this process, and each intermediate diagram was used as a good start to support the next iteration of our modelling. EMF class diagram creation The whole model is contained in one EMF class diagram. Here are the steps to create this.