Ah, I missed your comment that it would work from package or diagram. But my comments still hold. I don't think diagram is relevant and I think the context menu should build dynamically depending on what single model element has been selected. Same as happens now when multiple model elements are selected.
Bob. On 15/04/2008, Bob Tarling <[EMAIL PROTECTED]> wrote: > Hi Scott > > I'm surprised to see the options are selected on the context menu of > the diagram when I think the whole intention here is to create > elements without the diagram. If you create a class with this method > then how do you know what package to put it in? > > For node model elements (ie any model element that does not represent > a relationship between two others) I would have expected a context > menu that would be built depending on what specific single element had > been selected. > > e.g. > Context menu from package would give > CreateModelElement->CreateClass > CreateModelElement->CreateInterface > > Context menu from and namespace would give > CreateModelElement->CreatePackage > > Context menu from class would give > CreateModelElement->CreateAttribute > CreateModelElement->CreateOperation > > That list obviously isn't full, just thinking from the top of my head. > > The existing mechanism for creating model elements to relate 2 or more > other model elements works in that same way. From the context of what > you have selected. > > It would be great to see that work complete and consistent though. Good move. > > The current context menu item "Add Package" can be removed in favour > of this more consistent method. > > I'm not sure if there's a need for your second level breakdown of > diagram types as the diagram is not relevant here. If there is any > context menu that appear to grow far too large then we can take a look > at what to do for that. > > Cheers > > > Bob. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
