Eclipse Graphical Editing Framework (GEF) 3.10.1 (Mars.1) Release Review

End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.


3.10.1 (Mars.1)


The Graphical Editing Framework (GEF) 3.10.1 (Mars) provides:

  • Service revisions (3.10.1, 1.6.1) of the Draw2d 3.xGEF (MVC) 3.x, and Zest 1.x production components. Focus is on bugfixing only. All public API is preserved, binary compatibility is achieved.
  • Minor revisions (0.2.0) of the GEF4 components (GEF4 Common, GEF4 Geometry, GEF4 FX, GEF4 MVC, GEF4 Graph, GEF4 Layout, GEF4 Zest, GEF4 DOT, GEF4 Cloudio). Focus is on bugfixing, but incompatible changes to the provisional API are included, binary compatibility is not achieved.
API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues

There are no architectural issues concerning Draw2d, GEF (MVC), and Zest. With respect to GEF4, the following architectural issues are known and will be resolved after this release:

  • Splitting UI modules into SWT, JFace, and UI modules (470635)
  • Refactoring of GEF4 Zest JFace API (469330)
  • Refactoring of GEF4 Cloudio API (468707)
  • Splitting the documentation into user and developer documentation (465227)
  • Refactoring of GEF4 Zest.FX API related to semantic zooming (475190)
Security Issues

There are no security issues for this project.

Non-Code Aspects

Developer documentation for Draw2d 3.10.1, GEF (MVC) 3.10.1, and Zest 1.6.1 is provided in the form of a GEF Developer Guide (contributed via respective *.doc.isv bundles), as for previous releases. Documentation for the new GEF4 components has been newly build up on the GEF4 wiki pages on a per-component basis (and is extracted using Mylyn Wikitext into respective *.doc bundles). Javadoc is provided up to package visibility level throughout.

Examples for Draw2d 3.10.1 and Zest 1.6.1 are provided in the form of (unbundled) snippets, for GEF (MVC) in the form of (bundled) logic, shape, flow, and text editors. Examples for GEF4 MVC are provided in the form of (bundled and standalone) logo example, for GEF4 Zest in the form of a (bundled and standalone) graph example. For GEF4 FX, GEF4 Graph, GEF4 Layout, GEF4 DOT, GEF4 Geometry, and GEF4 Cloudio, examples are provided in the form of (unbundled) snippets. There are currently no examples provided for GEF4 Common (which is used in nearly all other components).


Usability Details

As GEF is a framework for building up graphical applications, most parts of the Eclipse User Interface Guideline are not directly applicable, because:

  • with the exception of GEF4 DOT and GEF4 Cloudio, none of the GEF components provide direct end-user functionality.
  • the UI of a graphical application, as supported by GEF, usually uses different means for user interaction compared to classical user (form-based) user interfaces.

Nevertheless, great attention has been spent on ensuring good usability. While usability has not been formally evaluated by end-users, the development of the GEF4 components has been supervised by a certified usability engineer in person of the project lead. Nevertheless, the usability of the GEF4 Cloudio and GEF4 DOT user interfaces is known to be still eligable for improvements (see 467033 and 337644).

End of Life

No officially released API has been deprecated/removed in this release. The changes to the provisional API are outined in GEF/New and Noteworthy/3.10.1.


There are no standards of relevance for this project.


The GEF project team as a whole interacts with its (adopters and users) community via bugzilla, the mailing list, and the forum. It also closely collaborates with the e(fx)clipse project team, which provides the JavaFX-OSGi integration used by most of the new GEF4 components.