On Apr 9, 11:56 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> they share the same longitudes. But it is reasonable to do it based on
> locale (including using the default locale setting).
Using the locale setting sounds great. Need any help?
--~--~-~--~~~---~--~-
Simon Litchfield said the following:
> Tad ugly though, don't you think? Most platforms/languages/frameworks
> handle the MDY/DMY situation relatively elegantly using some kind of
> setting.
Well I wasn't pitching it as the best solution, just *a* solution :p
--
Collin Grady
Of all forms of ca
On Tue, 2008-04-08 at 18:28 -0700, Simon Litchfield wrote:
[...]
> Am I not the only non-US guy who sees this as a major shortcoming in
> newforms?
It's not a forgotten corner, but we haven't fixed it yet. The idea is to
solve the entire problem, not just the one little piece that is date
time d
> I haven't tried to use it, but couldn't a DateTimeInput widget with those
> fields
> solve the problem? It accepts a format arg which is how it will render its
> data
> - combined with the right input_formats in the field, it stands to reason that
> would work :)
Yes you're right, so we can -
Simon Litchfield said the following:
> No control is given over how initial date/datetime values are
> rendered, using DateField/DateTimeField.
>
> Clients don't like -MM-DD; who can argue?
>
> At the very least, I propose we at least allow an optional
> display_format string, kinda like inp
No control is given over how initial date/datetime values are
rendered, using DateField/DateTimeField.
Clients don't like -MM-DD; who can argue?
At the very least, I propose we at least allow an optional
display_format string, kinda like input_formats.
More importantly though, I think we ca
