#16212: Improve multiple sort UX
-------------------------------------+-------------------------------------
               Reporter:  idangazit  |          Owner:  nobody
                   Type:  New        |         Status:  new
  feature                            |      Component:  contrib.admin
              Milestone:             |       Severity:  Normal
                Version:  SVN        |       Keywords:
             Resolution:             |      Has patch:  0
           Triage Stage:  Design     |    Needs tests:  0
  decision needed                    |  Easy pickings:  0
    Needs documentation:  0          |
Patch needs improvement:  0          |
                  UI/UX:  1          |
-------------------------------------+-------------------------------------

Comment (by idangazit):

 Just sat down to discuss this with Julien. In general, I'm unhappy with
 the multiple sort UI, and would prefer the fully-baked solution I've
 proposed. However, I don't see it happening in time for 1.4, and I'd like
 to make multiple sorting suck less for that release.

 Most of my feedback here is negative, just want to be clear that I like
 the general idea, just unsatisfied with the implementation we have now and
 the pain it could cause users. If it weren't painful, I'd remove multiple
 sort now and wait until we had a decent implementation before adding it.

 Regarding Julien's patch:

 * The additional cues and tooltips are good. The copy could be made
 friendlier, right now it's a mouthful.
 * Purely stylistically, the hover state of column headers isn't bad, but
 could be a little more subtle (gradient / darker grey -> flat highlight
 yellow is a big change).
 * I like the hover-on-sort-number-to-remove functionality.

 With this change, the only functionality still needed from the cog popover
 is the global "reset sorting" link. We can ditch the entire cog popover if
 we put that link elsewhere. My suggestion was to stick an additional div
 between the `.actions` and `.results`, containing the reset link. If
 multisort isn't active, the entire div can be hidden.

 Overall this is lipstick on a pig, but it's better than what we have, and
 we can get it into 1.4.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16212#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en.

Reply via email to