> # Disable selecting dates before or after a certain date This sounds like it should be general behaviour (adding min_date and max_date to DateField or something similar - I thought this was already in?).
I've got a couple more comments on admin UI in general, if you want to take a bite at them. For one it's kind of annoying the FKey/m2m/etc don't link either to the corresponding object's admin or site page if either are available (checking for admin first, then for site?). The fix should be very simple, just thought I'd add some FFT. I also filed ticket 10871 <http://code.djangoproject.com/ticket/10871 Add input support to admin actions (with patch)> a few days ago. I haven't had time to do anything recently but I'm curious what the general opinion on the design would be. Using an intermediate page as proposed in c2 sounds unnecessarily complicated if you just want something simple, to be honest. (Hope I'm not hijacking or something, saw this was on admin UI, hopped on it.) On Sat, Apr 25, 2009 at 5:02 AM, Jacob Kaplan-Moss <[email protected]> wrote: > > 2009/4/24 Jeremy Dunck <[email protected]>: >> I'm not sure what this means. Inline order is defined by the >> underlying queryset, isn't it? What would reordering them on the >> client do in the DB? > > This is a return of and a cleaning up of the old order_with_respect_to > (which still sorta works, but the admin feature depended on a > GPL-licensed JS lib, so we couldn't and didn't include it, and the > feature basically died). > > Jacob > > > > -- Adys --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
