Bug 370819 - [Global] A Flexible Drag & Drop framework
Summary: [Global] A Flexible Drag & Drop framework
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: M6   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard: Editors
Keywords: plan
Depends on:
Blocks: 388691
  Show dependency tree
 
Reported: 2012-02-07 07:39 EST by Camille Letavernier CLA
Modified: 2013-06-25 10:53 EDT (History)
3 users (show)

See Also:
rschnekenburger: juno+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Camille Letavernier CLA 2012-02-07 07:39:06 EST 
Papyrus should provide a flexible and customizable Drag & Drop framework.

The following cases should be handled:

- Drag & Drop between views
- Drag & Drop between a view and a Diagram
- Drag & Drop between a Diagram and a View
- Drag & Drop inside a Diagram

Currently, the GMF generated code handles most of the Drag & Drop cases in the diagrams. To make it flexible and customizable, a global reflection on the different mechanisms involved will be required.
Comment 1 Camille Letavernier CLA 2012-06-15 05:32:36 EDT 
Done in the following commits:

r8199, r8200, r8205, r8223 (Framework)
r8198, r8199, r8211, r8214, r8270 (UML Implementation)
Comment 2 Yann Tanguy CLA 2012-09-04 11:33:04 EDT 
This feature induce a regression in Composite Structure Diagram due to an incorrect wrapping of existing CreationEditPolicy (org.eclipse.papyrus.uml.diagram.composite.custom.edit.policies.PortInCompartmentCreationEditPolicy) on several edit parts.

This regression is described here: 
388691: [Composite Structure Diagram] Create a port on a class / property
https://bugs.eclipse.org/bugs/show_bug.cgi?id=388691
Comment 3 Camille Letavernier CLA 2013-06-25 10:53:44 EDT 
I close this task as it is now complete