-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Deployment diagram has wrong legend #94
Comments
Hi, I don't think boundaries need to be added to the legend. If we add deployment node to it, then we should probably add system, enterprise boundaries etc. There would be no real way to differentiate between them inside the legend. |
@adrianvlupu: Hi, do you remember the discussion as I started with the deployment diagram. You preferred the name "Node" and I told you it should be "Deployment_Node" (because boundary was my argument). But in the meantime I changed my mind and think your original idea with "Node" as element is better (I updated my implementation and used the name Node). The (Deployment_)Node is an element and not (only) a logical boundary therefore I think it should be part of the legend. |
…om tags/stereotypes support; dynamic legend supports custom colors, border and shadow; dynamic legend displays (only) used elements, tags/stereotypes. New added macros: SHOW_DYNAMIC_LEGEND(), AddTagSupport(), UpdateSkinparamsAndLegendEntry(), elements macros are extended with $tags="..."
…om tags/stereotypes support; ... (2 - update macros docu with added $tags="...")
Atm the deployment diagram uses the legend of container
Shouldn't we update it to soemthing like this
(I don't know how the border color can be changed therefore I used an emoji)
The text was updated successfully, but these errors were encountered: