Closed marek-piirikivi closed 1 year ago
@marek-piirikivi Thanks for the idea. I think #2213 is related to this, since it includes the idea that the boundary of a diagram represents the diagram kind.
It may be more friendly to use the abbreviated diagram type name.
E.g.
[cls] My Class Diagram
[act] My Activity
[sd] My Sequence Diagram
It may be more friendly to use the abbreviated diagram type name.
I would prefer not to diverge from the specification.
I just noticed that all this time I meant to use modelElementType instead of diagram kind. Indeed, type == kind in the standard. I'll fix that. Sorry for all the confusion.
I'll close this because #2540 added SysML specific header with necessary information. The minimal requirements for this issue have been met. I'll open a separate issue about the constraining.
Is your feature request related to a problem?
Diagram header only supports diagram name. It is not possible to explicitly know what modelElementType and model element (modelElementName) the diagram corresponds to. This is important information in SysML to properly navigate the model.
Describe the solution you'd like
This solution would promote correct SysML usage and improve user experience: a) by guiding users to use diagrams more correctly reducing the learning curve; and b) by simplifying model navigation and understanding of the model.
Describe alternatives you've considered
Currently, I have manually inserted necessary information into the diagram name. See the following example: This serves the purpose of the simplification of the model understanding.
Additional context
I would like to propose more details about the diagram modelElementType and modelElementName selection.
I would consider this issue complete with a minimum of having an option to select diagram kind and corresponding diagram kind elements from the dropdown; and auto-updating rendering of the diagram header.