I wouldn't be as sure about 0.3.1 having perfect i18n support. (maybe,
can't remember that anymore now either . ... I do remember where
important things like my car keys and home address are most of the
time though. ;) )
On 12/22/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
OK, one tacos port of d
OK, one tacos port of dojo date picker coming up in the next few days,
assuming it works in dojo 0.3.1, anyway. I'll base it one what you've
got in tap 4.1 so migration should be as painless as possible.
--sam
On 12/21/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Tacos uses this calendar :
h
Tacos uses this calendar :
http://www.dynarch.com/projects/calendar/
I don't think I've looked at the Tapestry "DatePicker" javascript yet
for any bugs so presumably it still has the same problem? (can't
remember all the changes made anymore )
On 12/21/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
We suffered this same problem, and unfortunately aren't using 4.1.x.
Both tacos and tapestry date pickers have this problem in tap 4.0.x.
Jess, what exactly was required for you to fix this? I haven't
looked, but I assume tacos is using the dojo date picker, so I should
be able to make similar ch
Nice. You avoided all the deprecated functions too (gotta love those Java
dates).
One gotcha I noticed was that the SimpleDateFormat objects are static, and
they're not thread safe by nature (at least according to the JavaDoc).
Those should probably be instance variables instead of statics.
Th
Thanks for noticing. I didn't follow the exact pattern that you
outlined but have made them rfc3339 compliant and things look much
better now.
Should be available at some point today.
On 12/15/06, Jon McCarty <[EMAIL PROTECTED]> wrote:
Hi everyone –
I'm enjoying the Tap4.1.1 line (I think tha
