thx, since I don't know python or django, just looking for some level of comfort I'm on track. Right now I'm actually playing with sub- classing a Field class and having *some* luck with it.
On Jun 6, 12:05 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 6/6/07, dailer <[EMAIL PROTECTED]> wrote: > > > > > looking for ideas on the best way to handle this. I have a need to set > > up date ranges not tied to a particular year, like Jan 1 - Feb 12. I > > like that the admin interface provides a date selector so I'm tempted > > to just use a DateField and ignore the fact that I would be selecting > > a specific year. I'm thinking the other option is to use a CharField > > to hold values like "Jan 1" and maybe try to rework the javascript for > > the date selector. > > Sounds like you already know what needs to be done. > > The first approach would be very low effort, but could be misleading > from a UI point of view; the second approach required writing a > customized widget. This isn't hard to do, but it does require more > effort. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
