Bug 469820 - Support Horizontal/Vertical stack layout for containers containing nodes
Summary: Support Horizontal/Vertical stack layout for containers containing nodes
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on: 436359
Blocks:
  Show dependency tree
 
Reported: 2015-06-10 05:50 EDT by Moritz Eysholdt CLA
Modified: 2015-06-16 05:00 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Eysholdt CLA 2015-06-10 05:50:56 EDT
In sirius git HEAD the method 
org.eclipse.sirius.diagram.editor.properties.section.description.containermapping.ContainerMappingChildrenPresentationPropertySectionSpec.shouldEnableCompartiments(ContainerMapping)
returns false when a container contains nodes or node imports. 
Consequently, the Layouts "Horizontal Stack" or "Vertical Stack" are disabled in the specification editor's properties view.

It would be awesome of the stack layout would work when the container's children are a mix of containers and nodes.
Comment 1 Maxime Porhel CLA 2015-06-12 10:25:17 EDT
Hi, thanks for your feedback !
This looks like an interesting area to explore. 

Sirius (3.0) supports only one level of compartiments, defined as List or FreeForm containers. It is already possible, at your own rick and without guarantee on user interactions (resize, ..), to describe some compartiments with compartiments inside: specifier will have to manually modify the attribute in a text editor. It is planned to work on it to remove this limitation (no fix version set yet).

But supporting nodes mappings as region/compartiment mapping has not been planned at all. This could be an interesting  improvement but will need deep work on the edit parts, layout, refresh, ...   It is not trivial and has impacts. 

At this point if you really want this changed you might want to sponsor the work or  possibly work on it yourself but please, do not engage 	in this before checking what we'll expect for integration in the source base:
 - builds and tests alive and wells
 - API compatibility and or/documented changes with deprecation policy
 - up to date documentation
 - models automatically migrated