How to move an existing diagram to another model/subsystem/package?

[xiao]

I have created a new empty project,and after completing a Use Case Diagram,I decided to create a Model and put my diagram in it.However,although I could "Cut and Paste" my diagram into the Model,the level of everything in the original diagram wouldn't change.In the "Model Explorer",rather than the children of the Model,items in the diagram is at the same level as the model.How could I move my diagram?

[Janusz Szpilewski]

Most likely you will need to drag & drop in the Model Explorer the existing diagram and its elements from their current model scope to the new one.

Cut/paste on the diagram only creates additional views without modifying the models themselves.

[xiao]

Got it,you saved my day!But I have to drag and drop my diagram and every item in it,which is quite tiring.Hope to improve it in the next realise.

[Janusz Szpilewski]

I agree that moving groups of elements one by one may be an annoying task. However the existing design of the Model Explorer is based on the assumption that only one element may be selected at time so extending that concept may not be a trivial task.

[Anonymous]

the elements belong to the model in UML, not to a Diagram. this because you can reuse them in different diagrams. Don't expect to move the diagram in some other model and see all the elements in the diagram move together! This would be totally wrong to be implemented, therefore Janusz, I would not even bother (imho).

The correct approach is to create another element that will contain all those elements and create the diagram within that context (could be a model ora package). If you do so, then you will get all elements directly created under that model, and if you want to move them, you will have to move that specific model. This is the correct MDA approach.

One thing would be nice though, Janusz, and it's related to the graphic enhancements we were talking about some posts ago.
I twould be really helpful to be able to have a Group/Ungroup feature on the pop up menu when you select multiple items on a diagram. In this way you can group things and move them around, facilitating the management. How much would you think it'd take?
Any progress on the palette side?

thanks in advance
TheCrazy

[Anonymous]

What about some additional features in the Draw and Notes section? (notes, free graphic, etc.) In this moment you can only create some ugly note and rectangular shapes.

TheCrazy

[Janusz Szpilewski]

I am considering a multi-selection in Model Explorer as a kind of shortcut for selecting and dragging elements one by one. However quite a few features internally assume that only one element in the Model Explorer is selected at time so I am afraid potentially some collisions may happen so it requires more attention. But some work was done, in StarUML it is not even possible to have selected simultaneously a model and a view on the diagram.

I suppose you consider grouping as some shortcut for selecting making sure that if one grouped element gets selected all other ones present on the diagram get selected too. I think it can be added as a feature probably in the diagram scope.

I think the major graphics update could be done after moving the graphics routines from current GDI to Direct2D what would allow to move diagram elements in their full form or use gradient or transparent colors. I have just started playing with that. All additional features could be added after. But it is rather a time consuming task so it will take some time to make it happen.

[Anonymous]

"the elements belong to the model in UML, not to a Diagram. this because you can reuse them in different diagrams. Don't expect to move the diagram in some other model and see all the elements in the diagram move together! This would be totally wrong to be implemented, therefore Janusz, I would not even bother (imho)."

AGREE!

One of the best features of StarUML is its very precise and elegant implementation of true UML standards and principle (OK- minor issue, it's not the latest UML version, but not a big problem for me). I think it's primary importance to stick to this UML true spirit otherwise the usability will suffer enormously. UML is the way it is because IT WORKS!

Thanks!