GEF/New and Noteworthy/3.10.1
- New and Noteworthy in 3.0
- New and Noteworthy in 3.5
- New and Noteworthy in 3.6
- New and Noteworthy in 3.7
- New and Noteworthy in 3.8
- New and Noteworthy in 3.9
- New and Noteworthy in 3.10
The GEF 3.10.1 (Mars SR1) release provides service releases for the production components Draw2d 3.x (3.10.1), GEF (MVC) 3.x (3.10.1), and Zest 1.x (1.6.1), as well as for the new GEF4 components (0.1.1).
Breaking changes of provisional API from 0.1.0 to 0.1.1
While GEF 3.10.1 (Mars SR1) is a bugfix release, some minor adjustments have been applied to the provisional API of GEF4.
DefaultSelectionProvider was moved (M1)
org.eclipse.gef4.mvc.fx.ui.DefaultSelectionProvider was moved to
org.eclipse.gef4.mvc.ui.DefaultSelectionProvider because it is independent of JavaFX.
FXMouseDragGesture, FXPinchSpreadGesture, and FXRotateGesture were renamed (M1)
FXRotateGesture abstract base implementations located in package
org.eclipse.gef4.fx.gestures were renamed to consistently use the 'Abstract' prefix:
org.eclipse.gef4.fx.gestures.FXMouseDragGesturewas renamed to
org.eclipse.gef4.fx.gestures.FXPinchSpreadGesturewas renamed to
org.eclipse.gef4.fx.gestures.FXRotateGesturewas renamed to
- The contract of
org.eclipse.gef4.mvc.fx.viewer.FXViewerwas changed so that it is no longer responsible of constructing a JavaFX scene and hooking it into an
FXVieweris now only responsible of constructing its own visuals (lazily within
#getScrollPane()) and hooking the root part visuals into it.
- The now obsolete
org.eclipse.gef4.mvc.fx.viewer.ISceneContainerabstraction and the related
org.eclipse.gef4.mvc.fx.ui.FXCanvasSceneContainerimplementations were removed.
GEF4 Geometry 0.1.1
Aligned background color within the examples and added window titles where missing (M1)
GEF4 Layout 0.1.1
Fixed a bug where dynamic layout was not applied although it should (M1)
GEF4 FX 0.1.1
GEF4 MVC 0.1.1
Fixed a bug where the undo history was incorrectly cleared (M1)
Enhanced the default resize mechanism for better customizability (M1)
You can now define the visual that is resized (only the part's "main" visual was allowed before), and also define the initial size (the visual's layout-bounds were used before).