Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 477352

Summary: Refactor FXTransformPolicy and related policies.
Product: [Tools] GEF Reporter: Matthias Wienand <matthias.wienand>
Component: GEF MVCAssignee: Matthias Wienand <matthias.wienand>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: nyssen
Version: 0.2.0   
Target Milestone: 4.0.0 / 3.11.0 (Neon) M2   
Hardware: All   
OS: All   
Whiteboard:

Description Matthias Wienand CLA 2015-09-14 07:10:12 EDT 
The FXTransformPolicy should provide an API for the manipulation of the transformation matrix of a visual part. This API should allow the user to perform transformations before the initial transformation matrix is applied, as well as, after the initial transformation matrix is applied. Moreover, the API should provide convenience methods for common transformations, such as translating in scene coordinates, rotating around a pivot point, and scaling around a pivot point. This should reduce the complexity when developing solutions using transformations.

Moreover, the related policies (FXRelocateConnectionPolicy, FXRelocateOnDragPolicy, FXResizeRelocateOnHandleDragPolicy, FXResizeRelocatePolicy, FXRotatePolicy, FXRotateSelectedOnHandleDragPolicy, FXRotateSelectedOnRotatePolicy, FXScaleRelocateOnHandleDragPolicy, and FXScaleRelocatePolicy) should be renamed to express the actual transformation (e.g. "translate" instead of "relocate"). Additionally, the intermediate FXResizeRelocatePolicy, FXRotatePolicy, and FXScaleRelocatePolicy should be removed. The policies that depend on those policies should use the FXTransformPolicy directly.
Comment 1 Matthias Wienand CLA 2015-09-25 10:02:47 EDT 
I reworked the API for FXTransformPolicy and updated the related policies accordingly. I renamed the policies to reflect their actual functionality. The code is published on the master branch. Therefore, I resolve this ticket as fixed for 3.11.0M2.