On Thu, 2008-10-09 at 00:30 -0700, David Christiansen wrote: [...] > Thanks for the explanation. Given that the reason for only ordering > on one field is that it's hard to design a UI to order on two, why not > just allow ordering on more than one field for the default ordering, > and then revert to single-field ordering when someone clicks the > column headers?
That's the normal question at this point. :-) One reason is that once you do ordering on one field, you can never get back to the original ordering (there's no UI to allow you to do that). So it's a one way operation, particularly if you accidentally click on something and ends up requiring an extra button to "reset to original ordering" or something. Not impossible to arrange, but it's an extra piece of UI that has to fit onto that screen. I've never really devoted any real time to that problem, since there's always been other things to do. If this is a real issue for you, the best thing is to come up with a solution that works for everybody and get it into Django. I'm not promising it will be easy, but there might well be a nice way to arrange for the "reset all ordering" to be relatively unobtrusive and then admin could allow multi-column ordering when specified on the model or ModelAdmin class. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
