| Summary: | Sequence and Collaboration diagram switching | ||
|---|---|---|---|
| Product: | [Applications] umbrello | Reporter: | Jonathan Riddell <jr> |
| Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | ralf.habacker |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Jonathan Riddell
2003-01-24 19:46:33 UTC
For the record I found several issue with this "switch" approach 1. The switch would only work for a very limited set of graphical elements. The sequence diagram provides a lot more graphical elements; several elements will be destroyed after a conversation to a collaboration diagram or need to be mapped. 2. Because the two diagrams uses different layout strategies, after converting an automatic layout has to be applied. 3. The implementation partially do not use the same type of widgets. While both diagram types are of class UMLScene and both object type are of ObjectWidget, the connections type are of MessageWidget for sequence diagrams and AssociationWidget for collaboration diagrams. Because these types are incompatible, a type conversation will loose some widget informations. 4. Changing the implementation to only use one type of class will result into an xmi incompatibility against older xmi file versions. 5. The switch is not reversible because of issue 1, 2 and 3. |