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

UML View syntax #37

Open
ronaldtse opened this issue Aug 6, 2020 · 8 comments
Open

UML View syntax #37

ronaldtse opened this issue Aug 6, 2020 · 8 comments

Comments

@ronaldtse
Copy link
Contributor

What syntax should we use for Views? I assume that the View syntax also has to be different per data model type (UML vs SysML vs EXPRESS) because they have different diagram requirements.

// or diagram MyView?
view MyView {
  import Relationship, Element
  render_option typed_as_associations
  file "my_view.png"
}

Originally posted by @ronaldtse in #15 (comment)

@ronaldtse
Copy link
Contributor Author

ronaldtse commented Aug 6, 2020

From @w00lf #8 (comment)

In UML model definition, these are equivalent:

class A
class B
A#foo -> B[1]
class A {
  foo: B[1]
}
class B

It is only the diagram that differs.
When we create the "view", perhaps we have the option of whether these associations are shown. (e.g. show generalization, aggregation but not simple association)?

What if we don't want to show specific generalization or aggregation?

For sure we should have a global turn "on" or "off" of types of relationships in the view.

Should we allow selectively showing of particular relationships?

@w00lf
Copy link
Contributor

w00lf commented Aug 9, 2020

What syntax should we use for Views? I assume that the View syntax also has to be different per data model type (UML vs SysML vs EXPRESS) because they have different diagram requirements.

// or diagram MyView?
view MyView {
  import Relationship, Element
  render_option typed_as_associations
  file "my_view.png"
}

Originally posted by @ronaldtse in #15 (comment)

I vote for diagram name, I think its more convenient, view we can use to set up specific display options(font, density, dpi)

@ronaldtse
Copy link
Contributor Author

I vote for diagram name, I think its more convenient, view we can use to set up specific display options(font, density, dpi)

Makes sense. Let's do it!

@ronaldtse
Copy link
Contributor Author

Then we have to come up with the View Syntax. Perhaps we can extend feature by feature. Any thoughts?

w00lf added a commit that referenced this issue Aug 13, 2020
…for lib/lutaml/uml/parsers/dsl.rb file
@w00lf
Copy link
Contributor

w00lf commented Aug 13, 2020

Then we have to come up with the View Syntax. Perhaps we can extend feature by feature. Any thoughts?

Lets start with diagram attributes first, view attributes will strongly depend on ogdf implementation.

@ronaldtse
Copy link
Contributor Author

Agree.

w00lf added a commit that referenced this issue Aug 17, 2020
@ronaldtse
Copy link
Contributor Author

@w00lf can we close this? Thanks.

@w00lf
Copy link
Contributor

w00lf commented Aug 5, 2021

@w00lf can we close this? Thanks.

Have not implemented it yet

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

No branches or pull requests

2 participants