-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Force-directed graph Layout Style #806
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Thanks for your input. I think you have a good point here in a general sense. Currently the layout mechanism is using a dagre algorithm. It would be powerfull to add the possibility to specify which layout algoritm to use. #867 I will close this one but link to it from #867. I will modify the syntax a bit. Default layout would for instance be current behavior. I dont want to breake a bunch of diagrams out there. |
Thanks. I appreciate the review |
The existing layout scheme is strictly hierarchical (TD, LR).
An organic layout should also be supported.
The organic layout above uses a predefined force-directed graph layout
The Class UML layout appears to operate in this manner, however, the class UML use case is currently limited to class diagrams because of the rendered box (with variable placeholders)
This issue will provide the following implementation:
graph Hierarchical TD
...
end
graph Organic
....
end
To address scenarios with subgraphs, the following approach could be used
graph Organic
subgraph Hierarchical TD
...
end
subgraph Hierarchical LR
...
end
end
The text was updated successfully, but these errors were encountered: