[katello-devel] multi-select in lists
Eric Helms
ehelms at redhat.com
Wed Nov 2 18:09:55 UTC 2011
On 11/02/2011 12:50 PM, Tyler Smart wrote:
> Tom, I agree with you. A user should not have to have a blank list before ctrl clicking.
>
> ----- Original Message -----
> From: "Tom McKay"<thomasmckay at redhat.com>
> To: katello-devel at redhat.com
> Sent: Wednesday, November 2, 2011 11:54:59 AM
> Subject: [katello-devel] multi-select in lists
>
>
> I'd like to raise how multiple items are selected in a list since it seems a bit non-intuitive to this user.
>
> Currently to select multiples the steps are:
> 1. Have nothing selected in list
> 2. Ctrl-click or shift-click to get the first item
> 3. Ctrl-click or shift-click to add more items
>
> It's that first step that really threw me off. The way list selection works elsewhere (every where else?) is:
> 1. Click an item
> 2. Ctrl-click or shift-click to add more
>
> Is there a reason for the difference in our list selection behavior?
>
> To further confuse the issue, ctrl-click of an already selected item does not unselect it but instead selects it, thus clearing all other selected items. In our current paradigm this now-selected item needs to be unselected before other items can once again be multi-selected.
>
> Hopefully that reads as bad as it feels to me. :)
>
> Thoughts?
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
Agreed that ctrl-click of an already selected item should un-select it
(in the multi-select case).
The reason for having to ctrl-click an item when none are selected to do
multi-selecting is due to the tupane paradigm. Say you normal click an
item from the list. You get the details page that slides out and
obstructs the right pane actions - the actions that were added last
sprint and can affect multiple items (e.g. for the systems page, Remove
Systems). Then, if you keep selecting items you can never perform
actions on them unless you manually click the 'close' button. I could
potentially see an argument for:
Nothing Selected:
Click an item - tupane details slide out
ctrl+click another item - tupane details slide back in and the user is
left in the 'mutli-select' state
Nothing Selected:
ctrl+click item when none selected provides current behaviour
Eric
More information about the katello-devel
mailing list