GEF/New and Noteworthy/3.7
Improved Mac OS X compatibility (M3, M4, M5, M6)
Special focus has been spent on resolving Mac specific inconsistencies. While some issues (e.g. proper key bindings) could be resolved directly within Draw2d/GEF, most of the problems were caused by underlying SWT inconsistencies, which were (identified by the GEF team and) resolved by the SWT team. Most notably, XOR painting mode is now supported by SWT on Mac Cocoa, which was the root cause for several issues on this platform, e.g. the incorrect painting of feedback figures.
Even while this has not been enforced via plug-in dependencies, it is thus recommended to use GEF 3.7 in combination with SWT/Eclipse 3.7, because you will not profit from these fixes otherwise. See bugzilla for a complete list of all Mac-specific issues that are resolved in 3.7.
Refactoring of Geometry API (M4)
Geometry API was refactored to guarantee consistency between integer-precision and double-precision version of
PrecisionRectangle. Synchronization between the still exposed integer-precision fields (x, y, width, height) and the no-longer exposed double-precision fields (preciseX, preciseY, preciseWidth, preciseHeight) is performed automatically by precision classes now, so clients may use the precision versions transparently, being no longer forced to perform a manual update of the respective fields. See 124904, 142628, and 271235 for details.
Refactoring of FlowLayout and ToolbarLayout (M5)
OrderedLayout was introduced as a new common superclass of
ToolbarLayout. As a consequence,
FlowLayoutEditPolicy could be generalized and may now work with
OrderedLayout, being no longer restricted to
FlowLayout based figures alone. See 88884 for details.
Refactoring of LayoutEditPolicy, ConstrainedLayoutEditPolicy, and XYLayoutEditPolicy (M4)
Layout edit policies have been refactored to remove duplicate code and allow better extensibility.
LayoutEditPolicywas enhanced by adding methods relevant for translations, used in all layout edit policies (removed duplicate code from subclasses):
getLayoutOrigin()(pulled up from
translateFromAbsoluteToLayoutRelative(Translatable t)(synthesized from duplicated code spread throughout different layout edit policies)
translateFromLayoutRelativeToAbsolute(Translatable t)(synthesized from duplicated code spread throughout different layout edit policies)
ConstrainedLayoutEditPolicywas changed as follows:
createAddCommand(ChangeBoundsRequest request, EditPart child, Object constraint)as a replacement for
createAddCommand(EditPart child, Object constraint), which was in turn deprecated (this is now handled similar as in case of change constraint commands).
createChangeConstraintCommand(EditPart child, Object constraint)concrete (empty body) and deprecated it to indicate that clients should instead
createChangeConstraintCommand(ChangeBoundsRequest request, EditPart child, Object constraint)
getConstraintFor(Request request, GraphicalEditPart child, Rectangle rectangle), which subsumes the duplicate code fragments located in
getConstraintFor(ChangeBoundsRequest request, GraphicalEditPart child)and
getConstraintFor(CreateRequest request)before (both of these methods now delegate to the new method).
XYLayoutEditPolicywas changed as follows:
- Replaced overwritten version of
getConstraintFor(ChangeBoundsRequest request, GraphicalEditPart child)with an overwritten version of the newly introduced
getConstraintFor(Request request, GraphicalEditPart child, Rectangle rect).
- Replaced overwritten version of
See 320852 for details.
Refactoring of Primary Drag Edit Policies (M4)
Primary drag edit policies were refactored to allow clients to easier provide custom handles and related select/drag/resize trackers.
NonResizableEditPolicywas changed by introducing hook methods to allow clients to customize the creation of handles and drag/select trackers used by them:
createDragHandle(List handles, int direction)
createMoveHandle(List handles, int direction)
createDragTracker(), which is used by
createDragHandle(List handles, int direction)to construct the drag tracker for the created drag handle.
createSelectTracker(), which is used by
createMoveHandle(List handles, int direction)to construct the select tracker for the created move handle.
ResizableEditPolicywas similarly changed by introducing the following methods:
createResizeHandle(List handles, int direction)
createResizeTracker(int), which is used by
createResizeHandle(List handles, int direction)to create the resize tracker for the constructed resize handle.
The refactoring was performed in combination with the enhancement of
CreationTool with support for constraints on resize and size-on-drop. See 67541 for details.
Enhancement of ResizeTracker and CreationTool (M4)
CreationTool so that they now offer means to enforce certain constraints (by default, minimum and maximum size constraints) during resize as well as size-on-drop (dragging during creation). This was realized by adding methods to enforce size constraints:
which are called whenever the source respectively target request is updated. By default, both ensure that minimum and maximum size constraints, which are inferred via respective hook methods:
Clients may overwrite the respective hook methods to infer maximum and minimum sizes for certain requests, or overwrite and adjust the enforcement of constraints as a whole (in case additional constraints have to be ensured). While the
CreationTool could already be easily exchanged with a customized subclass by specifying a tool class upon construction of a
ResizableEditPolicy was now enhanced to allow clients to specify a custom
ResizeTracker as well, which will be used for all resize handles.
The logic example was enhanced to demonstrate how the new features can be used. See 67541 for details.
Enhancement of MarqueeSelectionTool (M4)
MarqueeSelectionTool was enhanced to now offer the following default marquee behaviors:
- BEHAVIOR_CONNECTIONS_TOUCHED (supported since 3.1)
- BEHAVIOR_NODES_CONTAINED (supported since 3.1, default behavior)
- BEHAVIOR_NODES_CONTAINED_AND_RELATED_CONNECTIONS (supported since 3.1, formerly known as BEHAVIOR_NODES_AND_CONNECTIONS, which was in turn deprecated).
It was furthermore refactored to allow clients to customize marquee selection behavior via subclassing and overwriting one or more of the following methods:
The following methods are now also exposed (protected visibility) so clients can use access the current tool mode and the selection rectangle in their customization code:
The logic example was enhanced to demonstrate all new marquee behaviors. See 67991 for details.
Enhancement of MarqueeToolEntry (M4)
MarqueeToolEntry has been enhanced to use different icons dependent on the marquee behavior of the tool.
- BEHAVIOR_NODE_TOUCHED and BEHAVIOR_NODES_CONTAINED
- BEHAVIOR_CONNECTIONS_TOUCHED and BEHAVIOR_CONNECTIONS_CONTAINED
- BEHAVIOR_NODES_TOUCHED_AND_RELATED_CONNECTIONS and BEHAVIOR_NODES_CONTAINED_AND_RELATED_CONNECTIONS
See 185960 for details.
Exposition of MatchSizeAction (M4)
The logic example was enhanced to demonstrate use of the new action. See 107916 for details.
Refactoring/Exposition of UndoablePropertySheetEntry/UndoablePropertySheetPage (M6)
UndoablePropertySheetEntry was refactored and opened for subclassing (see 91257). An
UndoablePropertySheetPage was introduced, which uses the
UndoablePropertySheetEntry as its root entry and additionally supports the undo/redo of changes in case the associated editor is currently inactive (because the property view is active) by delegating to the editor's undo and redo actions (see 287684).
ResetValueCommand were refactored into a single
SetPropertyValueCommand, which was exposed as well (see 130721).