Unfortunately, where I work, the role of ID and UI
engineer are forced into 1 person: me. Therefore, I
don't have the luxury, authority, or maybe, the
self-discipline to suggest the hard-to-implement
drag-n-drop DHTML design.
I am leaning towards option (b) : The user changes the
order number in a textbox to change the row order, as
opposed to (a): provide up/down buttons and a
Here is my reasoning. Please comment.
There are numerous edit pages for this my.yahoo-style
front-end application, that require reordering of
items in a table. Some have a small number of
items(5-8), and others may have a large number(10-15).
To be consistent, I am chosing (b) for all, since
that seems like the necessary alternative for the
I would like to make things more WSYWIG. I can think
of 2 alternatives assuming option (b) :
(1) When the textbox with the order number loses
focus, automatically reorder the table at the client.
Will this be too surprising to the user? It seems like
(2) Place a link to update the order at the client.
Once the user has changed all the order numbers, the
user clicks the link to reorder.
Please comment. Don't respond "Go to some user testing
with both". :). Thanks.