Project Plan For modeling.gmp.graphiti, version 0.10.0
This document lays out the development progress for the Kepler version of Graphiti. The Graphiti release version will be 0.10.0, which means 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 future GEF4 version.
The release deliverables consist of the following items:
- Graphiti runtime binary distribution (ZIP file download and update site).
- Graphiti SDK/SDK+ (includes runtime, sources, examples, tools and documentation) (available as ZIP file download and update site). The SDK+ feature extends the Graphiti framework SDK with the optional SVG export and will contain more add-ons in the future.
- Graphiti tests (no download, executed in central Hudson build)
Graphiti will continue to be part of the Kepler release train at Eclipse.org. It will contain the framework, the examples, the tools and the tests. Graphiti has joined the release train within the Indigo M4 milestone.
For the Kepler release of Graphiti we plan to work on these bugzillas . In contrast to the ones above assigned to a specific milestone, the ones listed here are not yet assigned to a special milestone, but are planned to be targeted in the final Kepler release. Since we develop in Kanban mode and only plan roughly one sprint ahead; it is not possible before actually starting a sprint to tell which development topic will be in which milestone.
Additionally these bugs are candidates for working on in the Kepler timeframe.
Graphiti will support the same platforms as the Eclipse Platform project. For a list of platforms supported in Kepler, see Eclipse Target Operating Environments . The Graphiti project depends upon the Platform and other projects, which are mostly "pure" Java. The Kepler release of the Graphiti Project is written and compiled against version 1.5 of the Java Platform APIs, and targeted to run on version 1.5 of the Java Runtime Environment, Standard Edition. Graphiti will be tested and validated against a subset of those listed for the platform. The Kepler version of Graphiti will run against Eclipse 3.8 (Juno fallback), Eclipse 4.2 (Juno) and Eclipse 4.3 (Kepler).
The Graphiti framework only has a limited number of UI strings and dialogs, all texts come by default in English only, no language packs will be offered. The Graphiti framework and examples use Java resource bundles for storing texts and provide full internationalization support. Graphiti takes part in the Eclipse Babel translation process; translation packs can be downloaded from there.
Graphiti is still in the incubation phase and will stay with its Kepler release. There will be some API incompatibilities with the previous incubation release 0.9.0 to accomodate a round-off of the API. A list of those will be provided with the release review docuware. Workspaces and diagrams that were created with older versions of Graphiti will be compatible with the new Graphiti version provided with Kepler, meaning they still can be read and modified.
In the Kepler release of Graphiti the main focus is on improving the APIs, functional round-offs and improving the ease of use in standard scenarios. Some smaller enhancements are also planned.
Make Graphiti fit for leaving incubation
Fulfill the Eclipse requirements for being part of the Kepler release train and for leaving incubation after the Kepler release. Also some infrastructure related topics are planned like using Gerrit as review system the source code.
Round-Offs and ease of use
Fix inconsistent behavior in the framework and fill gaps in the functionality to make the framework easier to use.
Many small functional enhancements that were requested by the community in or after the Juno timeframe will be implemented.
Support for Eclipse 3.8 workbench
Graphiti will support 3.8 and 4.3 equally, all the functionality will be the same.
- Java is a trademark or a registered trademark of Sun Microsystems, Inc.
- All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.