-
Notifications
You must be signed in to change notification settings - Fork 480
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
[feature request] component and tab shapes #2228
Comments
The The |
Indeed I'm currently using d2 But d2 |
So the only difference between rectangle and the |
I need a shape for a component (category in Logtalk lingo) that visually helps distinguish from objects and protocols (interfaces), which uses a box/rectangle shape. But I don't see this as related to UML at all. Providing similar shapes to Graphviz helps projects compatibility and migration when generating diagrams. |
Would this feature suffice? (#1081 (comment)) Basically adding a |
My diagrams tool already supports an option that does just that. The text is printed below the label in a small font size. You can see an old example at: https://logtalk.org/diagrams/tools/tools_directory_load_diagram.svg |
That's not a d2 diagram. I thought you were looking for a feature in d2 diagrams for your use case. |
I am. I just provided that old example to show that what you described as "adding a << type >> to objects, distinct from label" is already implemented by Logtalk's diagrams tool, which currently supports both Graphviz dot and d2 graph language output files. It's a Logtalk user choice which graph language to use. I just upload a d2 version of the same diagram at: https://logtalk.org/diagrams/d2/tools_directory_load_diagram.svg The tool supported for d2 is currently marked as experimental, with the main feature missing being links in edges. |
It would be possible to provide a
tab
andcomponent
shapes as found in Graphviz (https://graphviz.org/doc/info/shapes.html)? This helps in generating similar diagrams when using d2 as an alternative to Graphviz.The text was updated successfully, but these errors were encountered: