Bug 431008 - [Usability] There are two different ways to load additional models which are called completely different things
Summary: [Usability] There are two different ways to load additional models which are ...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: dx, usability
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-24 08:58 EDT by Ronan Bar CLA
Modified: 2021-06-10 08:38 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ronan Bar CLA 2014-03-24 08:58:05 EDT
To load a second model via the Model Explorer I must do the following:

Select Model->Import->Import Package From Workspace then select a .uml file

To load a second model via the Diagram I must do the following:

Right click on the diagram and select "Load resource" and then select a .uml file (by the way it let's me select any file which is odd)

Now I have achieved the same thing via 2 completely different methods. Can't we just have the same method in both i.e. Load resource which only allows a .uml to be selected.
Comment 1 Camille Letavernier CLA 2014-03-24 14:04:22 EDT
"Load resource" is lower-level (EMF-technical), and allows more flexibility, but IMO, it shouldn't be presented to final users. Until recently, the "Import package" didn't provide any "Loading" support, and the Notation resources associated to imported libraries were not automatically imported. So, a manual "Load resource" was required.

Now that these two issues are fixed, the "Load resource" should probably not be available anymore.

Regarding the "Import package", it doesn't only load. It offers the choice between "Loading", "Copying" or "Importing". So, renaming it to "Load resource" might be confusing (For both end users and advanced users, because Advanced users might expect a true EMF "Load resource", instead of a UML-Specific Package importer/loader)
Comment 2 Ronan Bar CLA 2014-03-25 04:52:24 EDT
Aha! There is a big usability issue with the Import/Select the elements to import dialog. The action column provides a drop down list to select Load/Import/Copy but I never even noticed it was such a list! The drop down list only shows itself as a drop down list when you click on it. This is not obvious at all. I was wondering where these options had disappeared to. So this needs to be made more standard and more obvious.

I'm still not happy with the "Import" word as you are offering "Import", "Load" and "Copy". What about "Reuse Resource" or something better?

Also none of this is documented.
Comment 3 Christian Damus CLA 2014-03-25 07:59:05 EDT
(In reply to Ronan B from comment #2)
> 
> I'm still not happy with the "Import" word as you are offering "Import",
> "Load" and "Copy". What about "Reuse Resource" or something better?

The "Import" option literally creates a UML PackageImport relationship, a specific new model element.  The UML terminology is "import", so that seems most appropriate, here.

Perhaps something more along the lines of "Open" would be more generally understood than "Load"?

And drag-and-drop from Project Explorer to Model Explorer might be a convenient shortcut for opening another model, as an alternative to the import dialog.  (but this would be a separate new enhancement request, of course)
Comment 4 Ronan Bar CLA 2014-03-25 08:59:48 EDT
(In reply to Christian W. Damus from comment #3)
> The "Import" option literally creates a UML PackageImport relationship, a
> specific new model element.  The UML terminology is "import", so that seems
> most appropriate, here.
> 

Sure but import is just one of 3 things that can happen when I use this menu. If I wanted to create just a PackageImport I could do that using the PackageImport construct directly i.e. via New Child->Create PackageImport

> Perhaps something more along the lines of "Open" would be more generally
> understood than "Load"?

I'm not sure Open is create either as a copy or an import is not an "open"

> 
> And drag-and-drop from Project Explorer to Model Explorer might be a
> convenient shortcut for opening another model, as an alternative to the
> import dialog.  (but this would be a separate new enhancement request, of
> course)

True this would be nice.