My suggestion for handling the UI for multi-column sorts is to allow the definition of named sorts in a manner similar to the way that the default sorting is defined. With this in place, additional multi column orders can be accomplished simply by using this name as a sort selection and applying the corresponding named sort.
If this is an acceptable approach, I can flesh out the API for it. On Aug 11, 10:10 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > For those, like me, wondering what this proposal was about, it's > concerning changing sorting in the admin interface to initially use the > full set of fields specified in Meta.ordering on the model. > > What I can't work out yet, due to difficulty in reviewing the patch, > mentioned below, is whether it allow sorting by more than one column via > the column-clicking method. That would almost certainly seem to be a > request that is going to arrive 10 seconds after a feature like this is > committed, although the difficulty has always been with how the UI works > for that situation. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
