Bugzilla – Full Text Bug Listing
| Summary: | [req] Allow for logical diagram groups | ||
|---|---|---|---|
| Product: | [Modeling] GMF-Tooling | Reporter: | Richard Gronback <richard.gronback> |
| Component: | Core | Assignee: | gmf.generation-inbox <gmf.generation-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | gennady_vanin-eclipse |
| Version: | 1.0 | Keywords: | plan |
| Target Milestone: | 1.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Richard Gronback
Not sure what this means, really. The toolsmith is free to organize and target generation to whatever grouping is desired/required. Oooooh, UML! would be nice to have it? UML has: - attributes and stereotypes U may mark element or diagram with "isVisible", "isAbstract", "isLeaf", "isRoot",etc. - GeneralizableElement. It is a diagram or element that has no instances. It is possible to specify a grapelement/diagram (template) for further specification - COMPONENT Provides physical packaging for one or mre ModelElements - Diagram It is an abstract subtype of ViewElement. What is interesting is that ViewElement is not necessarily graphical, it may be textual - ComponentDiagram - DeploymentDiagram encompasse Components and Nodes - package, type (Everybody knows and/or does it) - stereotype It is extension mechanism. Someone can define its own stereotype with which to mark elements and thereafter, I guess, to group according to it - Viisibility. Though it is not only about graphics but in its more general meaning it is even more useful. [target cleanup] 1.0 M3 was the original target milestone for this bug [GMF Restructure] Bug 319140 : product GMF and component Definition was the original product and component for this bug |