> A dependency can exist between any 2 model elements. So a > context menu on the dependency list would need to popup some > dialog where the user can browse to any model element in the > repository. But this list already exists, on the explorer. > Why popup what we already have.
For this type of operation a user isn't going to be browsing, but rather doing a focused search for the single model element of interest. Tools which would help them focus include name substring matching, type selection, etc. This is somewhat different from role that the explorer pane fills. Also, as I mentioned before, all other instances in ArgoUML of adding a new item to a list use a context menu + popup to perform the operation. > The explorer tree allows you to select multiple items. The > actions to create for these are mostly very simple, usually > just delegating to the model facade to create. There's no GUI > to build to prompt the user for anything. Operations that require a user to navigate to and maintain selections on multiple elements, particularly if they can't see both simultaneously (ie have to scroll the explorer pane), tend to be pretty difficult to perform. If you're convinced the code is stable, I'm happy to have it remain, but not at the expense of having the functionality implemented where the users are going to first look for it (based on the current behavior). Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
