Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Renderer] Add custom layouts/containers for Regions #5

Open
CamilleLetavernier opened this issue Mar 22, 2018 · 1 comment
Open

[Renderer] Add custom layouts/containers for Regions #5

CamilleLetavernier opened this issue Mar 22, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@CamilleLetavernier
Copy link
Collaborator

Regions in a StateMachine Diagram can be freely arranged within a single StateMachine or Composite State. We should provide a custom Figure/Container to handle this.

The Regions container should have the same capabilities as in Papyrus, i.e. a set of nested Split Panes, which can be either Vertical or Horizontal:

statemachineregions

@CamilleLetavernier CamilleLetavernier added the enhancement New feature or request label Mar 29, 2018
@CamilleLetavernier
Copy link
Collaborator Author

CamilleLetavernier commented May 29, 2018

JavaFX SplitPanes won't work well with GEFx, due to conflicting event handlers. It might be possible to investigate this further and fix the issues.

Alternatively, we may use custom Handle Parts, installed between each Region when the StateMachine is selected, similar to what was done for CombinedFragments in Papyrus Sequence Diagrams:
cflayout

A simplified version of the Regions layout can be used also for Partitions in an ActivityDiagram (Swimlanes), or CombinedFragment in the Sequence Diagram, to separate Operands.

Partitions may be a little bit specific, as they can also look like a Grid (Whereas Regions are more flexible and don't need any symmetry)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant