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.
The main topics for 0.11.0 release of Graphiti were to continue working to enable Graphiti to eventually leave incubation and implementing round offs to make the framework more flexible and easy to use. however, Graphiti will stay in the incubation mode.
Graphiti is part of the Luna Eclipse release train since M2. Luna will contain the Graphiti framework, examples, tools and tests. Graphiti has joined the release train within the Indigo M4 milestone.
For the full list of changes and implementation details see the Graphiti New & Noteworthy page for 0.11.0.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
Graphiti’s architecture is solid and basically unchanged since the basis of the framework was already productive within SAP AG for several years. There were no changes from architecture point of view in the 0.11.0 timeframe.
Some parts of the framework coding needing some rework (e.g. in the rendering area) could not be addressed within this release and will be targeted for on of the next releases.
Graphiti will stay in the incubation mode. The reason for this is that there are too many open questions with respect to upcoming support for e4 RCP applications and the upcoming GEF4 version.
- The currently used GEF 3.x rendering appears to work fine but has several shortcommings/issues with rendering, e.g. off-by-one-issues. Fixing them would mean to invest massive effort within the Graphiti framework.
- GEF 4 or JavaFX offer themselves as alternative new rendering engines with much more future potential, but switching Graphiti to one of them also requires huge effort first in investigating these alternatives and second in writing a completely new UI layer for one of the frameworks.
The second alternative appears much more promising and seems to be the way to go. Unfortunatly, for both things there is currently no capacity in the available development resources. Unless there is much more engagement in framework development for Graphiti we can only stick to the current GEF 3.x based rendering engine and live with the limitations.
Leaving incubation should happen only after the new rendering engine is in place, because that change will require massive API changes throughout the complete framework.
Currently there is no indication that there are vulnerabilities within Graphiti.
- User documentation is available as part of the Graphiti SDK/SDK+ installation from the update site
- A large part of this documentation consists of a tutorial that introduces users step by step to the most common features of Graphiti
- The tutorial and documentation have been updated to reflect the changes done within the framework
- Further examples are part of our tests and can be synced from Git
- Website at http://www.eclipse.org/graphiti
- Graphiti can be downloaded via p2 update sites and as a zipped version
- Graphiti Feature (the framework)
- Examples Feature (includes examples, doc plugin with eclipse help integration and javadoc)
- Export Feature (diagram export to SVG)
- Tools Feature (tools that can be used to create Graphiti-based editors)
- SDK Feature (framework, examples, additionally includes sources to enable debugging)
- SDK+ Feature (additionally includes optional parts, currently the SVG exporter)
- Graphiti uses a Buckminster- and Hudson-based build and test infrastructure
- The framework plugins are provided with dedicated test plugins checking their valid behavior
Unit and SWTBotTests are executed as a part of the Buckminster Build on the Graphiti HIPP at Eclipse Hudson
- Each new build is tested at least with Eclipse 4.4 (Luna), another test environment is Eclipse 4.3 (Kepler)
- Graphiti is part of the Release Train since Eclipse Indigo (M4)
- Tutorial supports the getting started process for new users
- Good results in tool building can be achieved early
- Short turnaround cycles support incremental development
- Easy debugging enables fast problem solving (compared to frameworks based on code generation)
- Test preferences allow user to enable additional means to identify and analyze issues besides debugging
There are no deprecated or removed features within this release, but Graphiti switched from Java 1.5 to Java 1.6 as minimum runtime requirement within this development cycle.
- Execution Environment JavaSE 1.6, but also runs on Java 7
- Supports Eclipse Platforms 4.4 and 4.3
- Based on Draw2D/GEF 3.x and SWT, de-facto standards for graphics in Eclipse
- Integrated with and based on EMF, de-facto standard for modeling in Eclipse
- No native components, therefore there are no further requirements to the execution environment
- Bugs and enhancements are tracked using Bugzilla
- User feedback and enhancement request received
- Some contributions (bug fixes and enhancements) received
- Is used as active communication channel (~250 threads since last release 0.10.0)
- Many detail questions, discussions and enhancement ideas start there
- Developer mailing list
- Presentation at Eclipse Demo Camps for Kepler in Walldorf
- Several talks at EclipseCon 2013/14 referred Graphiti
Eclipse projects using Graphiti
- eTrice diagram editor
- JPA Editor diagram editor
- CDO/Dawn integrates with Graphiti
- BPMN2 Modeler diagram editor
Other open source projects refering to Graphiti
- Activity BPM Platform offers an Eclipse Designer built on Graphiti
- The KIELER research project integrates their layouting algorithms with Graphiti
- Spray supports a generative approach on top of Graphiti
Currently, Graphiti has only very limited development resources available, because most of the committers are no longer active in framework development. Especially therefore (but of course also in general) any contributions to the framework be it coding, documentation or other input is highly welcome. This is even more true for people who would like to become active in Graphiti framework development in the longterm and become committers for the project.