Thanks for the replies. I'm not really new to Django, but this is my
first application that I'm really building with it.
I never said that this should be in trunk or something, but if it will
get in, I would prefer something more customizable. However, it seems
that writing my own version that ju
Wow, a conversation about DurationField and I totally missed it. For
what it's worth, that patch needs a bit more work before even I want
it included in trunk. I've been putting it off because of my file
storage work, but I do plan to get back to it soon.
And Martin's right. Currently, DurationFi
It occurred to me, last night as I was drifting off to sleep, that the
only problem with just subclassing the DurationField widget, is that
you won't see any value over 24hrs, as that will spill over into days.
So - looks like your only option is to write your own version of
Duration Field.
I'm not sure why DurationField should be added to the core. It's
really easy to subclass MultipleValueField and MultiWidget.
In any case, from looking at DurationField, it seems that the defaults
for days, seconds, and microseconds are sane enough that you would
probably be safe to subclass
Hello,
I'm using the DurationField from
http://gulopine.gamemusic.org/2007/nov/03/storing-passages-of-time/
This is working fine, but the included widget shows text fields for
days, hours, minutes, seconds and microseconds. I would like to have
hours:minutes. The best solution seems to be that I
5 matches
Mail list logo
