You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jon McCarty <jo...@hotmail.com> on 2006/12/15 19:02:03 UTC
DropdownTimePicker, DropdownDatePicker, and time zones
Hi everyone –
I’m enjoying the Tap4.1.1 line (I think that’s where I am – I’m pulling from
svn trunk), but I had a problem with the Dojo-backed dropdown date and time
pickers.
Right now, they’re passing the dates to the client-side components in a way
that causes the client-side to do a timezone conversion. This throws off my
app when the client is in a different timezone than the server.
For my $0.02, the server should control all timezone issues – I want times
rendered as text to be the same as the ones in my widgets! I’d like to
recommend this change for the Tapestry trunk:
Change how we pass the date in DropdownDatePicker and DropdownTimePicker to
this code fragment:
Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
"," + value.getMonth() +
"," + value.getDate() +
"," + value.getHours() +
"," + value.getMinutes() +
"," + value.getSeconds() + ")");
json.put("value", formatted);
This works for both the date and time pickers. (Currently, the time picker
doesn’t work at all, probably due to a recent change in Dojo’s formatting
requirements.)
Comments? Should I open a JIRA to this effect?
--JM
--
View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: DropdownTimePicker, DropdownDatePicker, and time zones
Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <sg...@ideasculptor.com> wrote:
> 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 <jk...@gmail.com> wrote:
> > 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 <sg...@ideasculptor.com> 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 changes to tacos to get the same results.
> > > I've been putting off dealing with this for the better part of a week,
> > > but I'm going to have to dig into it soon.
> > >
> > > --sam
> > >
> > >
> > > On 12/21/06, Jon McCarty <jo...@hotmail.com> wrote:
> > > >
> > > > 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.
> > > >
> > > > Thanks for the fix!
> > > > Jon
> > > >
> > > >
> > > > Jessek wrote:
> > > > >
> > > > > 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 <jo...@hotmail.com> wrote:
> > > > >>
> > > > >> Hi everyone –
> > > > >>
> > > > >> I'm enjoying the Tap4.1.1 line (I think that's where I am – I'm pulling
> > > > >> from
> > > > >> svn trunk), but I had a problem with the Dojo-backed dropdown date and
> > > > >> time
> > > > >> pickers.
> > > > >>
> > > > >> Right now, they're passing the dates to the client-side components in a
> > > > >> way
> > > > >> that causes the client-side to do a timezone conversion. This throws off
> > > > >> my
> > > > >> app when the client is in a different timezone than the server.
> > > > >>
> > > > >> For my $0.02, the server should control all timezone issues – I want
> > > > >> times
> > > > >> rendered as text to be the same as the ones in my widgets! I'd like to
> > > > >> recommend this change for the Tapestry trunk:
> > > > >>
> > > > >> Change how we pass the date in DropdownDatePicker and DropdownTimePicker
> > > > >> to
> > > > >> this code fragment:
> > > > >>
> > > > >>
> > > > >> Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
> > > > >> "," + value.getMonth() +
> > > > >> "," + value.getDate() +
> > > > >> "," + value.getHours() +
> > > > >> "," + value.getMinutes() +
> > > > >> "," + value.getSeconds() + ")");
> > > > >> json.put("value", formatted);
> > > > >>
> > > > >>
> > > > >> This works for both the date and time pickers. (Currently, the time
> > > > >> picker
> > > > >> doesn't work at all, probably due to a recent change in Dojo's formatting
> > > > >> requirements.)
> > > > >>
> > > > >> Comments? Should I open a JIRA to this effect?
> > > > >>
> > > > >> --JM
> > > > >>
> > > > >> --
> > > > >> View this message in context:
> > > > >> http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
> > > > >> Sent from the Tapestry - User mailing list archive at Nabble.com.
> > > > >>
> > > > >>
> > > > >> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Jesse Kuhnert
> > > > > Tapestry/Dojo team member/developer
> > > > >
> > > > > Open source based consulting work centered around
> > > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a8013696
> > > > Sent from the Tapestry - User mailing list archive at Nabble.com.
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: DropdownTimePicker, DropdownDatePicker, and time zones
Posted by Sam Gendler <sg...@ideasculptor.com>.
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 <jk...@gmail.com> wrote:
> 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 <sg...@ideasculptor.com> 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 changes to tacos to get the same results.
> > I've been putting off dealing with this for the better part of a week,
> > but I'm going to have to dig into it soon.
> >
> > --sam
> >
> >
> > On 12/21/06, Jon McCarty <jo...@hotmail.com> wrote:
> > >
> > > 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.
> > >
> > > Thanks for the fix!
> > > Jon
> > >
> > >
> > > Jessek wrote:
> > > >
> > > > 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 <jo...@hotmail.com> wrote:
> > > >>
> > > >> Hi everyone –
> > > >>
> > > >> I'm enjoying the Tap4.1.1 line (I think that's where I am – I'm pulling
> > > >> from
> > > >> svn trunk), but I had a problem with the Dojo-backed dropdown date and
> > > >> time
> > > >> pickers.
> > > >>
> > > >> Right now, they're passing the dates to the client-side components in a
> > > >> way
> > > >> that causes the client-side to do a timezone conversion. This throws off
> > > >> my
> > > >> app when the client is in a different timezone than the server.
> > > >>
> > > >> For my $0.02, the server should control all timezone issues – I want
> > > >> times
> > > >> rendered as text to be the same as the ones in my widgets! I'd like to
> > > >> recommend this change for the Tapestry trunk:
> > > >>
> > > >> Change how we pass the date in DropdownDatePicker and DropdownTimePicker
> > > >> to
> > > >> this code fragment:
> > > >>
> > > >>
> > > >> Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
> > > >> "," + value.getMonth() +
> > > >> "," + value.getDate() +
> > > >> "," + value.getHours() +
> > > >> "," + value.getMinutes() +
> > > >> "," + value.getSeconds() + ")");
> > > >> json.put("value", formatted);
> > > >>
> > > >>
> > > >> This works for both the date and time pickers. (Currently, the time
> > > >> picker
> > > >> doesn't work at all, probably due to a recent change in Dojo's formatting
> > > >> requirements.)
> > > >>
> > > >> Comments? Should I open a JIRA to this effect?
> > > >>
> > > >> --JM
> > > >>
> > > >> --
> > > >> View this message in context:
> > > >> http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
> > > >> Sent from the Tapestry - User mailing list archive at Nabble.com.
> > > >>
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > > --
> > > View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a8013696
> > > Sent from the Tapestry - User mailing list archive at Nabble.com.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: DropdownTimePicker, DropdownDatePicker, and time zones
Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <sg...@ideasculptor.com> 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 changes to tacos to get the same results.
> I've been putting off dealing with this for the better part of a week,
> but I'm going to have to dig into it soon.
>
> --sam
>
>
> On 12/21/06, Jon McCarty <jo...@hotmail.com> wrote:
> >
> > 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.
> >
> > Thanks for the fix!
> > Jon
> >
> >
> > Jessek wrote:
> > >
> > > 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 <jo...@hotmail.com> wrote:
> > >>
> > >> Hi everyone –
> > >>
> > >> I'm enjoying the Tap4.1.1 line (I think that's where I am – I'm pulling
> > >> from
> > >> svn trunk), but I had a problem with the Dojo-backed dropdown date and
> > >> time
> > >> pickers.
> > >>
> > >> Right now, they're passing the dates to the client-side components in a
> > >> way
> > >> that causes the client-side to do a timezone conversion. This throws off
> > >> my
> > >> app when the client is in a different timezone than the server.
> > >>
> > >> For my $0.02, the server should control all timezone issues – I want
> > >> times
> > >> rendered as text to be the same as the ones in my widgets! I'd like to
> > >> recommend this change for the Tapestry trunk:
> > >>
> > >> Change how we pass the date in DropdownDatePicker and DropdownTimePicker
> > >> to
> > >> this code fragment:
> > >>
> > >>
> > >> Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
> > >> "," + value.getMonth() +
> > >> "," + value.getDate() +
> > >> "," + value.getHours() +
> > >> "," + value.getMinutes() +
> > >> "," + value.getSeconds() + ")");
> > >> json.put("value", formatted);
> > >>
> > >>
> > >> This works for both the date and time pickers. (Currently, the time
> > >> picker
> > >> doesn't work at all, probably due to a recent change in Dojo's formatting
> > >> requirements.)
> > >>
> > >> Comments? Should I open a JIRA to this effect?
> > >>
> > >> --JM
> > >>
> > >> --
> > >> View this message in context:
> > >> http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
> > >> Sent from the Tapestry - User mailing list archive at Nabble.com.
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > >
> >
> > --
> > View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a8013696
> > Sent from the Tapestry - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: DropdownTimePicker, DropdownDatePicker, and time zones
Posted by Sam Gendler <sg...@ideasculptor.com>.
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 changes to tacos to get the same results.
I've been putting off dealing with this for the better part of a week,
but I'm going to have to dig into it soon.
--sam
On 12/21/06, Jon McCarty <jo...@hotmail.com> wrote:
>
> 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.
>
> Thanks for the fix!
> Jon
>
>
> Jessek wrote:
> >
> > 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 <jo...@hotmail.com> wrote:
> >>
> >> Hi everyone –
> >>
> >> I'm enjoying the Tap4.1.1 line (I think that's where I am – I'm pulling
> >> from
> >> svn trunk), but I had a problem with the Dojo-backed dropdown date and
> >> time
> >> pickers.
> >>
> >> Right now, they're passing the dates to the client-side components in a
> >> way
> >> that causes the client-side to do a timezone conversion. This throws off
> >> my
> >> app when the client is in a different timezone than the server.
> >>
> >> For my $0.02, the server should control all timezone issues – I want
> >> times
> >> rendered as text to be the same as the ones in my widgets! I'd like to
> >> recommend this change for the Tapestry trunk:
> >>
> >> Change how we pass the date in DropdownDatePicker and DropdownTimePicker
> >> to
> >> this code fragment:
> >>
> >>
> >> Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
> >> "," + value.getMonth() +
> >> "," + value.getDate() +
> >> "," + value.getHours() +
> >> "," + value.getMinutes() +
> >> "," + value.getSeconds() + ")");
> >> json.put("value", formatted);
> >>
> >>
> >> This works for both the date and time pickers. (Currently, the time
> >> picker
> >> doesn't work at all, probably due to a recent change in Dojo's formatting
> >> requirements.)
> >>
> >> Comments? Should I open a JIRA to this effect?
> >>
> >> --JM
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
> >> Sent from the Tapestry - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a8013696
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: DropdownTimePicker, DropdownDatePicker, and time zones
Posted by Jon McCarty <jo...@hotmail.com>.
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.
Thanks for the fix!
Jon
Jessek wrote:
>
> 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 <jo...@hotmail.com> wrote:
>>
>> Hi everyone –
>>
>> I'm enjoying the Tap4.1.1 line (I think that's where I am – I'm pulling
>> from
>> svn trunk), but I had a problem with the Dojo-backed dropdown date and
>> time
>> pickers.
>>
>> Right now, they're passing the dates to the client-side components in a
>> way
>> that causes the client-side to do a timezone conversion. This throws off
>> my
>> app when the client is in a different timezone than the server.
>>
>> For my $0.02, the server should control all timezone issues – I want
>> times
>> rendered as text to be the same as the ones in my widgets! I'd like to
>> recommend this change for the Tapestry trunk:
>>
>> Change how we pass the date in DropdownDatePicker and DropdownTimePicker
>> to
>> this code fragment:
>>
>>
>> Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
>> "," + value.getMonth() +
>> "," + value.getDate() +
>> "," + value.getHours() +
>> "," + value.getMinutes() +
>> "," + value.getSeconds() + ")");
>> json.put("value", formatted);
>>
>>
>> This works for both the date and time pickers. (Currently, the time
>> picker
>> doesn't work at all, probably due to a recent change in Dojo's formatting
>> requirements.)
>>
>> Comments? Should I open a JIRA to this effect?
>>
>> --JM
>>
>> --
>> View this message in context:
>> http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a8013696
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: DropdownTimePicker, DropdownDatePicker, and time zones
Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <jo...@hotmail.com> wrote:
>
> Hi everyone –
>
> I'm enjoying the Tap4.1.1 line (I think that's where I am – I'm pulling from
> svn trunk), but I had a problem with the Dojo-backed dropdown date and time
> pickers.
>
> Right now, they're passing the dates to the client-side components in a way
> that causes the client-side to do a timezone conversion. This throws off my
> app when the client is in a different timezone than the server.
>
> For my $0.02, the server should control all timezone issues – I want times
> rendered as text to be the same as the ones in my widgets! I'd like to
> recommend this change for the Tapestry trunk:
>
> Change how we pass the date in DropdownDatePicker and DropdownTimePicker to
> this code fragment:
>
>
> Object formatted = new JSONLiteral("new Date(" + (value.getYear()+1900) +
> "," + value.getMonth() +
> "," + value.getDate() +
> "," + value.getHours() +
> "," + value.getMinutes() +
> "," + value.getSeconds() + ")");
> json.put("value", formatted);
>
>
> This works for both the date and time pickers. (Currently, the time picker
> doesn't work at all, probably due to a recent change in Dojo's formatting
> requirements.)
>
> Comments? Should I open a JIRA to this effect?
>
> --JM
>
> --
> View this message in context: http://www.nabble.com/DropdownTimePicker%2C-DropdownDatePicker%2C-and-time-zones-tf2828601.html#a7896437
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org