| Summary: | [Class Diagram] remove the default palette | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Patrick Tessier <Patrick.Tessier> | ||||||
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | Keywords: | plan | ||||||
| Version: | 0.7.0 | ||||||||
| Target Milestone: | M1 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | UML 2.x Diagrams | ||||||||
| Attachments: |
|
||||||||
|
Description
Patrick Tessier
Created attachment 136183 [details]
mylyn/context/zip
impacted elements
Created attachment 136184 [details]
mylyn/context/zip
impacted classes
done We need to have a common organization between diagrams to be consistent. Have the same tool group, same names: for example do we use links, relationships or connections ? I agree with you, for the names it tried to take name of abstract classes for example. |