Bug 455056 - Allow edges between items within separate list containers
Summary: Allow edges between items within separate list containers
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
: 498781 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-12 11:08 EST by Tom Manning CLA
Modified: 2016-11-02 12:30 EDT (History)
6 users (show)

See Also:

Attachments
Example (109.25 KB, image/png)
2014-12-12 11:08 EST, Tom Manning CLA 		no flags Details
Specification: Edge towards items in list containers (136.45 KB, application/x-zip-compressed)
2014-12-12 13:30 EST, Steve Monnier CLA 		no flags Details
View All 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 Tom Manning CLA 2014-12-12 11:08:47 EST 
Created attachment 249393 [details]
Example

As per forum post https://www.eclipse.org/forums/index.php/t/639877/

I would like Sirius to allow me to specify edge connections between individual nodes contained within list-based container nodes, rather than just edges between container nodes themselves. Image attached to see what this looks like.
Comment 1 Steve Monnier CLA 2014-12-12 13:30:44 EST 
Created attachment 249396 [details]
Specification: Edge towards items in list containers

Here is a specification document that was written concerning this evolution.
Comment 2 Pierre-Charles David CLA 2015-01-20 04:25:47 EST 
Moving to 3.0 at least to refresh the spec and evaluate the impacts. At first glance it would require relatively deep changes in our GMF code, so it should probably be done only after some simplifications are aleady done (see  bug #456343), and may overlap with other changes in this area which will be needed for bug #436359.
Comment 3 Pierre-Charles David CLA 2015-12-15 04:11:11 EST 
Moving out of the 4.0 scope for now, along with all the other issues which were there "by default". This does not mean some of these will not be re-integrated at some point, but for now these issues are not part of the roadmap for 4.0.

If you feel strongly about this removal from 4.0 and/or are ready to sponsor the corresponding work, feel free to comment.
Comment 4 Cedric Brun CLA 2016-07-28 11:08:45 EDT 
*** Bug 498781 has been marked as a duplicate of this bug. ***