Attaching diagrams to elements

[Martin Terreni]

well..I guess we should also distinguish aggregation.

[Paolo F Cantoni]

I should think the composite must also have ownership of its Meronyms.  Or, are you including aggregates in this discussion as well?

Yes, Jim...  I forgot...  Ownership, in this case being the ability to destroy...

Paolo

[jeshaw2]

Ownership, in this case being the ability to destroy...

And perhaps exclusive access to the Meronyms. Only by me may you access my parts.

However, Eric Evans (of DDD fame) does allow multiple root aggregates. Is that a factor also?

My apologies if I'm muddying up the water here.

[KP]

To the <context Menu>Advanced> sub menu:

1) If the element is structural, add the Composite Element menu item and the Show Composite Diagram Contents (which, by the way, should be disabled is the element isn't composite).  Actioning the first option, will create a Composite Structure Diagram below the element.  Actioning the second, displays the contents of that diagram.
2) In addition, add a new menu item Attach Diagram to Element.  If this is actioned, a tabbed dialog displays.  One tab shows a browser to allow the user to browse for an existing diagram, the other tab displays the new diagram dialog will be opened asking for the type of diagram to create.  If a new diagram is requested, it is added below the element, otherwise the browsed for diagram is attached.  As with the Composite element menu options, an additional Show Attached Diagram Contents item (again, disabled if there is no attached diagram) allows the display of the diagram.
NOTE: If Composite Element is true, then Attach Diagram to Element is disabled (and vice versa).  That is, you can only set one of the options if none are currently set.
3) If the element is non-structural, then only the Attach Diagram to Element functionality is available.  This also applies to instances of structural elements.

Paolo, I refactored your suggestion then refactored some more until I came up with a one-liner that is (IMO) a vast improvement:

All diagram objects should have "Add Diagram" and "Link to Diagram" commands on their context menu, making the "Composite Element" command redundant.

I think it maintains the spirit of your suggestion and addresses all the issues, so I have logged it as a feature request. It is not trivial to implement, so it will have to go through the approval process, of course.

I think the only issue not addressed is the fact that the "Show Composite Diagram Contents" command needs to be hidden when there's nothing to show. That's an easy fix.

[sargasso]

Reflecting elsewhere  

All diagram objects should have "Add Diagram" and "Link to Diagram" commands on their context menu, making the "Composite Element" command redundant.

All diagram objects clearly (and umbiguously ((?sp)) )includes the word [glb]edges[/glb]. ... ...

bruce

[jeshaw2]

And also extends to declared operations within class elements??

[Martin Terreni]

What about elements actually being part of (destroyed with) the containing (composite) element?

[KP]

Reflecting elsewhere  

All diagram objects clearly (and umbiguously ((?sp)) )includes the word [glb]edges[/glb]. ... ...

bruce

With EA the way it is, there's no way to add a child diagram to an element that doesn't appear in the Project Browser, so having an "Add Diagram" command for edges is impossible without a huge redesign. I can't think of any major obstacles to a "Link to Diagram" command for edges though (but where would you put the "0-0" link symbol?)

And also extends to declared operations within class elements??

Practical problem here is that, with the current schema, a diagram assumes its owner is in the t_object table which operations aren't - not insurmountable, just troublesome. I can't think of any major obstacles to a "Link to Diagram" command for operations.

What about elements actually being part of (destroyed with) the containing (composite) element?

My view is that is best handled by the user in the Project Browser and would add too much baggage to the suggested commands. If you want a composite or structured element (whatever your definition of those terms is), then the "Add Diagram" and "Link to Diagram" commands can help you create one but shouldn't actually define what one is (which is why the "Composite Element" command causes such confusion).