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

Enhancement: Update artifact element notation. #14

Closed
adamboduch opened this issue Nov 16, 2009 · 5 comments
Closed

Enhancement: Update artifact element notation. #14

adamboduch opened this issue Nov 16, 2009 · 5 comments

Comments

@adamboduch
Copy link
Contributor

Artifacts should be displayed as a classifier stereotyped as a artifact.

@amolenaar
Copy link
Member

What we really need is stereotype icons and a switch option. That way a user can change between the text (<>), the icon in the classifier or just the icon. Actor is a typical example of only an icon (it can be displayed as stereotyped class too).

@adamboduch
Copy link
Contributor Author

What if a given class in some profile is extending some meta class in order to become a stereotype. Perhaps when the extending class is selected, the element editor dialog contains the advanced stereotype selectors (like icon).

Or, what about quick streotypes that users need to apply to classes but don't feel it necessary to create a profile? Maybe the element editor can allow for simple streotype creation when a class is selected? Maybe this functionality is a Gaphor plugin candidate?

Just some thoughts.

@amolenaar
Copy link
Member

In case 1 I was thinking about selecting the way it is presented by a selector on the stereotyped class (so it can be determined per diagram).

  1. One of the thing I want is that all information is in a diagram. I'm not sure if and why one would like to have stereotypes that are not visualized. Well, maybe if you would use a template profile that is not in the actual model. (templating still has to be worked on though).

@adamboduch
Copy link
Contributor Author

I agree entirely about having the stereotypes visualized. I was thinking more for users with less UML experience.

Presentation on a per class basis also makes sense.

@amolenaar
Copy link
Member

This issue was closed.
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