|
We have a queue on our users' project page. And we want to introduce sequencing. Currently all actions that are applied are First In; First Out. What is the best method for sequencing? We have come up with a number of ways, but feel they each have their downfalls.
If possible also include an example of the method you believe is best. |
|||||||||
|
|
As @LarsTech says, all of the above. Plus: if the items in the queue have a shared set of attributes, you can also offer sorting the queue by attribute column. Also, option 3 can be extended with "click arrows to move item to front/end of list", which is efficient but does ask users to think in reverse. Another consideration: please make your interfaces accessible, which means don't purely rely on drag and drop. Which is best? So .. is this an interface for expert users or novice/intermittent users? Do you have a strong need for accessibility? What is the common mental model users have with this queue? And the Jakob maxim: users spend 90% of their time on other websites, experiencing their conventions, so don't go getting too clever with designing specific to their quirks. |
|||
|
|
|
As long as the queue isn't too long (doesn't hold more items that can fit vertically on screen) then I say go for the drag & drop. Make sure you use some sort of grip on the side of each item to indicate that it's drag-able. |
|||
|
|
|
How about a button that says something like "Set order", and then displays the message "Click actions in the desired order of execution (you can always change that)". The user clicks through the list, with an indication of the number of the current step ("Set step #7"). The order is reflected by numbers on the actions. When they click "done", actions are rearranged in the right order. From there, up/down arrows and drag & drop should work well for adjustments. Letting them edit the numbers manually can turn into a major headache for everyone. Let's say I want to switch between steps 5 and 9. How do I go about it? If I type "9" in the box of the current 5, then for a second I have two steps number 9 and no step number 5. If I delete both values first, then for a second I have no steps 5 and 9. Of course it can all be solved if you make them enter a special "edit" mode with validation at the end, but it just makes everything much more cumbersome, and the complexity of your UI just went up a couple of notches. |
|||
|
|
|
Personally, I like the up and down arrows approach, but then I am a techy, and I think this appeals to my understanding best. For none-technical people, I would suggest dragging, because it is most intuitive (IMO) - you pick up something and put it where it needs to go, and everythign else sorts itself out. I think you need to pick between these depending on your audience. The sequence numbering is a bad idea. I think it is a difficult idea to interpret, even though it seems obvious. It is fine to show sequence numbers, but trying to reorder using them is not easy. |
|||
|
|
