Skip to main content
Jump to: navigation, search

Difference between revisions of "GEF/New and Noteworthy/4.0"

m
 
(27 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
* [http://www.eclipse.org/gef/newandnoteworthy/New-and-Noteworthy-30.html New and Noteworthy in 3.0]
 
* [http://www.eclipse.org/gef/newandnoteworthy/New-and-Noteworthy-35.html New and Noteworthy in 3.5]
 
* [[GEF/New and Noteworthy/3.6| New and Noteworthy in 3.6]]
 
* [[GEF/New and Noteworthy/3.7| New and Noteworthy in 3.7]]
 
* [[GEF/New and Noteworthy/3.8| New and Noteworthy in 3.8]]
 
* [[GEF/New and Noteworthy/3.9| New and Noteworthy in 3.9]]
 
* [[GEF/New and Noteworthy/3.10| New and Noteworthy in 3.10]]
 
* [[GEF/New and Noteworthy/3.10.1| New and Noteworthy in 3.10.1]]
 
  
== General ==
+
The "New & Noteworthy" pages have been migrated to GitHub:
  
The [https://projects.eclipse.org/projects/tools.gef/releases/4.0.0-neon GEF 4.0.0 (Neon)] release provides minor revisions of the maintenance components [https://www.eclipse.org/gef/draw2d/ Draw2d 3.x] (3.11.0), [https://www.eclipse.org/gef/gef_mvc/index.php GEF (MVC) 3.x] (3.11.0), and [https://www.eclipse.org/gef/zest/index.php Zest 1.x] (1.7.0), as well as major revisions of the new [[GEF/GEF4|GEF4]] components (1.0.0).
+
* [https://github.com/eclipse/gef/blob/master/CHANGELOG.md#gef-400-neon GEF@github.com CHANGELOG]
 +
* [https://github.com/eclipse/gef-legacy/blob/master/CHANGELOG.md#gef-400-neon GEF-Legacy@github.com CHANGELOG]
  
''As declared in the [https://projects.eclipse.org/projects/tools.gef/releases/4.0.0-neon/plan project plan], the decision about contributing GEF4 in version 1.0.0 (instead of 0.3.0) and an overall 4.0.0 release (instead of 3.11.0) was postponed up to M5. That is, Bugzilla entries commented before Neon M6 will refer to a 3.11.0 release and milestone contributions (including M5) include GEF4 components in version 0.3.0.''
+
[[Category:GEF]]
 
+
Please note that several incompatible changes to the (up to 0.2.0 provisional) API of GEF4 were made. The list of added and removed classes is documented in the  [https://www.eclipse.org/gef/project-info/GEF4-0.2.0-1.0.0-API-Diff.html GEF4 0.2.0-1.0.0 API Diff]. The most notable API changes are outlined below.
+
 
+
----
+
 
+
== GEF4 Common (1.0.0) ==
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=484774 #484774] As outlined in detail in [http://nyssen.blogspot.de/2016/04/gef4-common-collections-and-properties.html 'GEF4 Collections and Properties - Guava goes FX'] the property notification support provided by [[GEF/GEF4/Common |GEF4 Common]] has been replaced with JavaFX observable collections and properties. In this turn, the [[GEF/GEF4/Common |GEF4 Common]] component has been augmented to provide observable collections and related collection properties for Guava's SetMultimap and Multiset, as well as replacements for the ObservableSet, ObservableList, and ObservableMap collections and related collection properties provided by JavaFX.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=482972 #482972] The adapter map injection support, described in detail in [http://nyssen.blogspot.com/2014/11/iadaptable-gef4s-interpretation-of.html Adaptable - 'GEF4's interpretation of a classic'], has been updated to ensure that adapter can always been retrieved via their actual runtime type, as well as been augmented with support for role-based adapter injection.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=481677 #481677] Adapter bindings can now be restricted to an adaptable of a certain role. Thereby, different bindings can e.g. be provided for a 'content' FXViewer and a 'palette' FXViewer.
+
 
+
----
+
 
+
== GEF4 FX (1.0.0) ==
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=471154 #471154] Renamed FX.UI module into FX.SWT module and added FXColorPicker, FXSimpleLinearGradientPicker, and FXAdvancedLinearGradientPicker, which were provided by MVC.FX.UI module before (refactored from AbstractFXColorPicker, FXColorPicker, FXSimpleGradientPicker, and FXAdvancedGradientPicker). Introduced new FX.JFace module, which provides FXPaintCellEditor and FXPaintSelectionDialog, which were provided by MVC.FX.UI module before (refactored from FXFillCellEditor and FXFillSelectionDialog).
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=479395 #479395] Merged ScrollPaneEx and FXGridCanvas into InfiniteCanvas. The FXGridLayer has been removed and its functionality was moved to the newly created InfiniteCanvas. The InfiniteCanvas does now allow to insert visuals at different "positions" inside of the InfiniteCanvas: underlay group, scrolled underlay group, content group, scrolled overlay group, overlay group.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=454681 #454681] Added support to Connection for having a clickable area that is thicker than the connection stroke and allows to select also very thin connections. Its width is exposed by a property of Connection, so it can be bound (e.g. to adjust the width of the clickable area dependent on the scaling). Enhance the MVC logo example to demonstrate example usage of this feature.
+
 
+
* Added support for proper clipping of decorations
+
* Ensured that the curve node of a connection can be replaced
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=488356 #488356] Introduced support for orthogonal routing of a Connection, including support for start and end point hints. While doing so, separated routing (manipulation of control points) from interpolating (visual appearance), so that routers (straight, orthogonal) and interpolators (poly-line, poly-bezier) can be freely mixed.
+
 
+
[[File:ConnectionSnippet.jpg|206px]]
+
 
+
* Exposed all relevant properties as (observable) properties, so it can be better used in a pure JavaFX environment.
+
 
+
* Revised DynamicAnchor and its IComputationStrategy to be comparable to a JavaFX binding, where the resulting position value is based on observable computation parameters that might depend on the anchorage (static) or anchored visual (dynamic).
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=443954 #443954] GeometryNode has been revised to extend Region instead of Parent, so it no longer relies on overriding the deprecated impl_computeLayoutBounds() method that is deprecated and announced to be removed in future JavaFX releases. The API of GeometryNode was enhanced so that it does now allow to use relocate(double, double) and resize(double, double) to update the layout bounds (including layoutX and layoutY) while relocateGeometry(double, double) and resizeGeometry(double, double) can be used to update the geometric bounds. The layout bounds (and layoutX, layoutY) resemble the geometric bounds, expanded by a stroke offset (dependent on stroke width and type) and border insets.
+
 
+
----
+
 
+
== GEF4 MVC (1.0.0) ==
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=477352 #477352] The FXTransformPolicy now provides an API for the creation and manipulation of transformation matrices. These matrices are then concatenated, together with the initial host transformation matrix, to yield the new host transformation matrix. Therefore, complex transformations can be set up properly at one point, and the important values can be changed later on, e.g. during user interaction. All transaction and interaction policies related to transforms (FXRelocateConnectionPolicy, FXRelocateOnDragPolicy, FXResizeRelocateOnHandleDragPolicy, FXResizeRelocatePolicy, FXRotatePolicy, FXRotateSelectedOnHandleDragPolicy, FXRotateSelectedOnRotatePolicy, FXScaleRelocateOnHandleDragPolicy, and FXScaleRelocatePolicy) have been renamed to express the actual transformation (e.g. "translate" instead of "relocate"). Additionally, the intermediate FXResizeRelocatePolicy, FXRotatePolicy, and FXScaleRelocatePolicy have been removed. The policies that were dependent on those intermediate policies are now directly using the FXTransformPolicy.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=479612 #479612]  Cleaned up ContentPolicy to only provide operations related to the content of the respective host part. It is intended to be registered at each IContentPart. Moved all "higher-level" operations into CreationPolicy and DeletionPolicy, which are to be registered at the IRootPart alone.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=480875 #480875] Updating the selection, hover, and focus models is now handled within the CreationPolicy and the DeletionPolicy and the ClearHoverFocusSelectionOperation has been removed. The CreationPolicy selects and focusses a newly created part. The DeletionPolicy removes the deleted parts from the selection and focus models. Moreover, the CreationPolicy creates the IContentPart before executing operations on the history. Therefore, the content part can be used for live feedback even though the creation is not yet committed.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=481600 #481600] Changed the implementation of ContentBehavior to ensure that deactivation does not remove children of its host. This way, deactivation of an FXViewer can now be temporarily applied (to disable all listeners) without loosing the content of the viewer.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=488358 #488358] In addition to straight routing based on circle handles, FXBendFirstAnchorageOnSegmentHandleDragPolicy and FXBendConnectionPolicy now supports orthogonal routing based on rectangle handles. Analogously to the way point based case, white handle can be used to create new segments, whereas solid handles are used to move segments. Overlay of segments and 'normalization' (i.e. removal of overlaid segments) are performed during interaction.
+
 
+
[[File:Straight_Routing_PolyBezier_Interpolator.jpg|250px]] [[File:Orthogonal_Routing_Polyline_Interpolator.jpg|250px]]
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=493553 #493553] IDomain now accepts only ITransactionalOperations to execute. This allows to filter non content-related operations (like selection of focus change) in case only content-relevant changes should be undoable.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=481677 #481688] The MVC Logo example has been augmented by a fly-out palette for object creation to demonstrate how multiple viewer can be combined in a single domain.
+
 
+
[[File:Palette_for_object_creation_001.png|250px]] [[File:Palette_for_object_creation_002.png|250px]] [[File:Palette_for_object_creation_003.png|250px]] [[File:Palette_for_object_creation_004.png|250px]] [[File:Palette_for_object_creation_005.png|250px]]
+
 
+
----
+
 
+
== GEF4 Layout (1.0.0) ==
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=491097 #491097] The LayoutContext and ILayoutAlgorithm now use a [[GEF/GEF4/Graph |GEF4 Graph]] data model as input and output model for layout calculations instead of its own layout interface abstractions.
+
 
+
----
+
 
+
== GEF4 Graph (1.0.0) ==
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=480293 #480293] Enhanced the builder API so that graph-, node-, and edge-builders can be chained appropriately. Node-builders can now be provided with an Object-key, that can be referred to by edge-builders.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=484774 #484774] Adopted API to expose all relevant properties through JavaFx observable collections/properties.
+
 
+
----
+
 
+
== GEF4 Zest (1.0.0) ==
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=470636 #470636] Separated out the Zest JFace-API into an own module (Zest.FX.JFace), so it can be consumed without introducing dependencies on the Eclipse Workbench UI.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=478944 #478944] Removed IEdgeDecorationProvider from Zest.FX.Jface. Respective ZestProperties.EDGE_SOURCE_DECORATION and ZestProperties.EDGE_TARGET_DECORATION attributes may be provided via IGraphNodeLabelProvider#getEdgeAttributes() instead.
+
 
+
----
+
 
+
== GEF4 DOT (1.0.0) ==
+
 
+
The [[GEF/GEF4/DOT | GEF4 DOT]] component has been completely revised and has made significant progress towards a full DOT authoring environment. It does not provide public API yet and is currently limited to provide end-user functionality.
+
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=446639 #446639] A Graphviz preference page has been added, via which the path to the native dot executable and the Graphviz export format can be specified.
+
 
+
[[File:Graphviz_Preference_Page.jpg|400px]]
+
 
+
* A 'Sync Graphviz Export' toggle has been added as an action of the DOT editor to the main toolbar (it was previously located in the DOT Graph view). If enabled, it will export the persisted state of a currently edited DOT file in the format specified in the preferences.
+
 
+
[[File:Sync_Graphviz_Export.jpg|20px]]
+
 
+
* The DOT Graph view will now use the native dot executable (if specified via the preferences) for layout (native mode), while it will otherwise use a comparable [[GEF/GEF4/Layout | GEF4 Layout]] algorithm (emulated mode).
+
 
+
[[File:DOT_Graph_view_native.jpg|400px]] [[File:DOT_Graph_view_emulated.jpg|400px]]
+
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=477980 #477980] The DOT Graph view now also provides additional rendering capabilities, including edge decorations, splines, as well as all available kind of labels (for edges and nodes).
+
 
+
[[File:DOT_Graph_view_rendering_capabilities.jpg|400px]]
+
 
+
* The DOT editor has been enhanced with additional validation support for arrowtype, point, splinetype, shape, and style attribute values.
+

Latest revision as of 10:20, 9 June 2017


The "New & Noteworthy" pages have been migrated to GitHub:

Back to the top