| Summary: | [GEF4] Provide new MVC component | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Alexander Nyßen <nyssen> |
| Component: | Misc | Assignee: | Alexander Nyßen <nyssen> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.9.100 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Alexander Nyßen
The existing GEF MVC related stuff (EditParts, etc.) should be transferred into a GEF4 MVC component, where it can be migrated to use GEF4 Geometry and GEF4 SwtFX. We should use this bug to keep track of the work and to at first collect all design flaws of the existing GEF component that need to be resolved. - Remove palette dependencies from EditDomain (see bug #365524). - Remove inconsistent usage scenarios related to EditPartMap (373168) - Make GraphicalEditPart#getContentPane more flexible (420503) - Replace GEF command framework (125991) Created an initial prototype and a small related JavaFX example (which is continually improved). The newly created features (MVC, MVC UI, MVC FX) have been integrated into the integration build, the example is available from the Git repo. Enhanced the example with an Eclipse UI integration for the FX-related parts (MVC.FX.UI), which now provides an Eclipse UI view (which uses SwtFX for the integration and thus provides support for touch gestures) that also hooks into the workbench's IOperationHistory to support undo/redo. We are currently reworking the feedback (we will introduce an IFeedbackPart and a related IFeedbackPartFactory) and handle mechanisms (both will be refactored to work on handle and feedback geometries), which I expect to be completed by this or next week. The component has been created and the initial example has reached a certain maturity. Resolving this as fixed. All other work should be done in terms of decimated bugzillas. |