Hi All, Let me clarify my thoughts about the Message Notation, i.e. currently 2 classes: MessageNotationUml and SDMessageNotationUml.
I split them myself, for issue 5150 - one for the collaboration diagram, one for the sequence diagram. But now I am not even sure yet we need 2 different classes. IIUC from the standard, then the Message notation for both diagrams should have the same capabilities. We may choose to show one or more optional part less or more in one diagram as opposed to the other, though. Maybe (1) we don't introduce a difference at all, or (2) make things selectable by the user with different defaults per diagram. And the "things" are at least: showing sequence numbers. If we make them selectable per diagram, then that would be the first time we have a setting with diagram scope - not a step lightly to take IMHO. PS: Christian offered to work on uniting the 2 classes with an abstract superclass containing the common code - maybe the best way to guarantee that we can merge them later. I'll try to look at the Message notation parsing (issue 5150). Regards, Michiel ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1002253 To unsubscribe from this discussion, e-mail: [[email protected]].
