Bug 447715 - Ease the specifcation of edge reconnection tools
Summary: Ease the specifcation of edge reconnection tools
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks: 525257
  Show dependency tree
 
Reported: 2014-10-17 10:31 EDT by Maxime Porhel CLA
Modified: 2017-09-27 03:49 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Porhel CLA 2014-10-17 10:31:24 EDT
There is currently a hidden variable named otherEnd which is the non reconnected end of the edge. 

It was created to avoid unreadable expression to identify what needs to be done on reconnect tools with 'reconnectionKind = both'.

But it could be usefull to display it in available variables for source only and target only reconnect tools especially when the edge is defined by a Relation Based Edge Mapping with several instances on the diagram. In those cases, all the edges have the same target element: the semantic element of the source node, and to identify the other end semantic, the specifier needs to known the Sirius Diagram metamodel and to add it to the DiagramDescription.metamodels feature. Then he can write requests like [edgeView.targetNode.oclAsTypeOf(EdgeTarget).target/] (which could require additional elements to avoid Acceleo compilation warning or errors).

But if we provide in the proposals or in the variables displayed in the VSM, two variable nonReconnectedEnd and nonReconnectedEndView (names to review later), it will ease the spefication of reconnection tools and avoid many questions.