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. On Tue, 2009-08-11 at 20:21 -0100, Joshua Russo wrote: > On Tue, Aug 11, 2009 at 7:46 PM, Rock <r...@rockhoward.com> wrote: > > Yes. I have a project that could use this immediately. Looking > forward > to seeing the ticket and a patch I can try out. > > > Ok, let me know what you think. > http://code.djangoproject.com/ticket/11695 Please read contributing.txt about how to submit patches. I looked at the latest patch on that ticket and it wasn't complete. Then I realised you have filed three patches that all need to be read together. This makes reviewing extremely difficult. It also means that if somebody fixes a problem in one of the patches, it becomes incredibly unclear which are the relevant patches. Creating svn diffs isn't difficult. You change to the top of the source tree and run "svn diff". All your changes in one patch with full paths. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
