Community
Participate
Working Groups
In the plugins import wizard, if you pick the defaults (esp. "select from all plugins..." then on the 3rd "Selection" page you will see a list of available plugins on the left and the task is to fill the list on the right with those you want. This dialog is overwhelming and could be improved in a few ways: - The list of 8 buttons with arrows pointed left, right, or both, is like one of those confusing road signs. For example see http://www1.istockphoto.com/file_thumbview_approve/914882/2/istockphoto_914882_confusing_traffic_sign.jpg. - The most common buttons could be grouped together (preferable at the top) with the less common grouped below, with space between the groups. While keeping the same number of buttons, it allows easier scanning of them. - It seems some buttons are dependent on selection while as others are not, yet there is nothing to indicate this. Ideally the buttons would somehow look different but a start would be disabling buttons which rely on selection state when nothing is selected. - The purpose of some buttons is not obvious. For example, "Existing Plugins" vs. "Existing Unshared". Incidentally, the help provides no clarification. - It might be possible to reduce the number of buttons. For example, Cntrl-a nicely does a select-all on the list, so I could live without an "Add All -->" button. Similar for "<-- Remove All", although I can see arguments for keeping them to speed the typical actions (I usually want all the plugins (add all), or I made a mistake (remove all). Also, the utility of the "Swap" button isn't clear to me except maybe for some complex sequence like "add the one I *don't* want then swap to get all but it". - We need a better visual than the "-->" "<--" ascii arrows (which aren't translation friendly anyway).
Created attachment 72270 [details] Screen shot of wizard Screen shot highlights a few issues: 1. The ascii arrows (red) 2. Top layout of bottons should align with top of lists (green line). This might make the dialog feel a little less crammed.
let's get input from Dani, who imports a million times a day.
Most of the time when I use the importer I do this: 1. click 'Existing Unshared' 2. click 'Finish' >- The most common buttons could be grouped together Agree. I also agree on the missing enablement state update of buttons that depend on a selection. >- The purpose of some buttons is not obvious. For example, "Existing Plugins" >vs. "Existing Unshared". This is pretty obvious too me. What do you not understand here Kevin? >- It might be possible to reduce the number of buttons. For example, Cntrl-a >nicely does a select-all on the list Sorry but I use the mouse and not the keyboard and it would be loss of function if that button gets removed. So far I've never used the 'Swap' button and I guess it wouldn't hurt to remove it.
First off, I'm not sure if Dani is the typical user, he's an expert user, and my concern is that this dialog is overwhelming for many. Note too that I am assuming that importing is something that a new PDE developer will do since they may want to see the source of dependent plugins etc. So this dialog is not just for advanced users. (In reply to comment #3) > >- The purpose of some buttons is not obvious. For example, "Existing Plugins" > >vs. "Existing Unshared". > This is pretty obvious too me. What do you not understand here Kevin? It doesn't seem this is a term we use often and I'm not sure where a new to semi experienced user will have come across it prior to this wizard. To add to the confusing, there's the menu "Team->Share Project". Note also: - the F1 help for the wizard doesn't describe it - I did a search in our help for "shared plug-ins" and the first 4 hits didn't help An idea might be that buttons like that select the given plugins in the left list. Although it makes it now two steps, at least the user can see which ones are "shared" (and thus have an indication of what it means) before moving them. > >- It might be possible to reduce the number of buttons. For example, Cntrl-a > >nicely does a select-all on the list > Sorry but I use the mouse and not the keyboard and it would be loss of function > if that button gets removed. Well come on I think "loss of function" is a bit dramatic (besides, you should use the keyboard more Dani, its better for your wrists <g>). The point is that when you have this big column of buttons the eye doesn't know where to land and its hard to know where to start. Each has a cost. You guys can debate if you think "Select-All" is worth it. Perhaps if the overall layout etc. were cleaned up then the added cost per button would be reduced (for example, if we had a small button beside the list with a special select-all symbol and we used that everywhere in Eclipse, it'd be much less intrusive).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
