In the new admin sorting UI, which now supports sorting on multiple
fields, the behaviour can be described by the following two rules:
1. If you click on a header, it is made the primary sort field
(with others moved down the list as necessary).
2. If you click on a header that was already part of the sorting,
the sort order for that field is reversed.
Item 1. is behaviour we agreed on, and item 2. is too, kind of, but the
latter is the one I'm interested in tweaking.
Currently, this means that if, for example, you do:
1) Click 'first name' header
2) Click 'last name' header
3) Click 'first name' header
you build up the following sort:
1) Sort by first name ascending
2) Sort by last name ascending, then
first name ascending
3) Sort by first name *descending*, then
last name ascending
It is this last step that might need improving. Is it confusing that you
end up with first name *descending*?
We could change the 2nd rule to:
2. If you click on a header that was already the primary sort field,
the sort order for that field is reversed.
I think this might be more intuitive. Comments?
Luke
--
"Where a person wishes to attract, they should always be ignorant."
(Jane Austen)
Luke Plant || http://lukeplant.me.uk/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
