Jump to: navigation, search

Difference between revisions of "GEF/GEF4"

< GEF
Line 1: Line 1:
[[GEF/GEF4 | GEF4]] is the unified effort to develop a new GEF 4.0 code base as a modernization of the current one (Draw2d and GEF (MVC) 3.x and Zest 1.x, in the following referred to as ''GEF proper''). Being developed in parallel to maintaining the GEF proper code base, [[GEF/GEF4 | GEF4]] is set up as a provisional component in order to not being bound to the same API compatibility constraints. Up to now development has been started by creating a new double-precsision Geometry API (see Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=355997 355997] for details) based on the Draw2d Geometry classes as a nucleus. Plans are to port the remaining parts of the Draw2d and GEF (MVC) 3.8 code base to it after the Juno release, as well as the up to now independently developed Zest2 code base (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=372365 bug #372365] for details).
+
[[GEF/GEF4 | GEF4]] is the unified effort to develop a new GEF 4.0 code base as a modernization of the current one (Draw2d and GEF (MVC) 3.x and Zest 1.x, in the following referred to as ''GEF proper''). Being developed in parallel to maintaining the GEF proper code base, [[GEF/GEF4 | GEF4]] is set up as a provisional component in order to not being bound to the same API compatibility constraints. Up to now development has been started by creating a new double-precsision Geometry API (see Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=355997 355997] for details) based on the Draw2d Geometry classes as a nucleus. As this is nearing completion, creation of a new Graphics API (see Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=386029 386029] for details), which abstracts from a concrete windowing toolkit and can be used in SWT and AWT context (we assume that JavaFX might become interesting as an Eclipse RCP rendering possibility on the near term), is the next logical step. After this, the remaining parts of the Draw2d and Zest2 code base can be migrated, and after it GEF (MFC).
  
 
== Components ==
 
== Components ==
  
 
* [[GEF/GEF4/Geometry | GEF4 Geometry]]
 
* [[GEF/GEF4/Geometry | GEF4 Geometry]]
 +
* [[GEF/GEF4/Graphics | GEF4 Graphics]]
  
 
== Bugs/Enhancements ==
 
== Bugs/Enhancements ==

Revision as of 07:45, 26 July 2012

GEF4 is the unified effort to develop a new GEF 4.0 code base as a modernization of the current one (Draw2d and GEF (MVC) 3.x and Zest 1.x, in the following referred to as GEF proper). Being developed in parallel to maintaining the GEF proper code base, GEF4 is set up as a provisional component in order to not being bound to the same API compatibility constraints. Up to now development has been started by creating a new double-precsision Geometry API (see Bugzilla 355997 for details) based on the Draw2d Geometry classes as a nucleus. As this is nearing completion, creation of a new Graphics API (see Bugzilla 386029 for details), which abstracts from a concrete windowing toolkit and can be used in SWT and AWT context (we assume that JavaFX might become interesting as an Eclipse RCP rendering possibility on the near term), is the next logical step. After this, the remaining parts of the Draw2d and Zest2 code base can be migrated, and after it GEF (MFC).

Components

Bugs/Enhancements

There is no specific Bugzilla component to classify bugs for GEF4. Up to now, all bugs that are related to GEF4 are thus prefixed [GEF4]. Here is a list of all bugs currently related to GEF4.

Source Code

After the Juno release, the complete source code of the GEF4 provisional component will be located in the GEF4 Git repository. Up to now it only includes the GEF4 Geometry in its current state as well as the already existing release engineering infrastructure. The source code of the Zest2 component can now be found in the Zest Git repository.

Update Sites

A Tycho-based build infrastructure for the GEF4 provisional component has been configured under https://hudson.eclipse.org/hudson/job/gef4-nightly-tycho. The build job is triggered hourly in case of changes to the source code repository and further once per day. It produces an update-site, which does not get promoted to downloads.eclipse.org, but can directly be consumed from:

In addition to this, integration, milestones, and release builds are promoted to downloads.eclipse.org and can be found here:

Note that while integration builds are promoted automatically once per week (every friday), milestone and release builds are published only manually on the respective occasions (not yet). Further note that these update sites are merged (so old builds are preserved), while the nightly update site gets replaced on each build.

Additional Information