Mickael,
To re-state, I really like the idea and appreciate what you have
done. I just think we can find a better user experience.
See comments below.
On 01/04/2016 9:30 AM, Mickael Istria
wrote:
The
current implementation brings the developer immediately into an
MPC search but provides no context on why they are there. It
seems to me a new wizard would solve this problem.
What would be the content of such a wizard?
At a minimum, we need to have a UI that states 'here are some
suggestions to associate with this type of file'. The system editor
needs to be one potential option. I also don't think we need all the
other UI elements in the MPC.
Currently, the only thing that relate the file to the context is
the description of the Marketplace entry. So if one opens an .erl
file, they see the MPC wizard (not really guessing what's
happening) and then they see the Erlang plugin entry explaining
that it's support for Erlang in the IDE. That's how users
"reconnect" the wizard to their action.
So two things 1) I think it is a large leap to go from trying to
open a file to where you are asking to install new software. This is
not a normal pattern. 2) what happens if there are multiple choices
or worst lots and lots of choices. In my mind this creates even more
confusion.
Maybe rather than a new wizard, the MPC wizard could accept a
"wait message" that would be shown why the catalog is polled. In
the case of installation, it could be something like "Contacting
marketplace to find good editor support for file ...".
WDYT?
I actually like what Max has suggested in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176
--
Ian Skerrett
VP of Marketing
Eclipse Foundation
(m) 613-240-7210
(o) 613-224-9461 ext 227
(t) @ianskerrett
|