I think it should work, but I'm not absolutly sure. Since you can't
select the time zone in the calendar (hopefully!), you may be right to
avoid transfering timezone information, because it could change the day
when going from/to the server to/from the client.
Example.
I'm at GMT+11. If write the
The fix I implemented was to use a simple number (milliseconds since
the epoch) as the transfer format. I'm concerned there may be a time
zone issue though, when the browser time zone is not the same as the
server time zone.
On Tue, Oct 14, 2008 at 4:59 PM, Mikaël Cluseau <[EMAIL PROTECTED]> wrot
itself. AFAIK, it work flowlessly.
>
--
View this message in context:
http://www.nabble.com/Tapestry-5.0.15-DateField-localization-problem-tp19723586p19989363.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
Well I still had stability problems under IE (surprise!) so I tried to
fix the thing in Tapestry itself. AFAIK, it work flowlessly.
Comments welcome ;)
Index:
/home/nwrk/workspaces/isi/hatch/tapestry-core-svn/src/main/java/org/apache/tapestry5/corelib/components/DateField.java
==
Well... for this to work cleanly, you also need to add an "if" around
the whole datefield-tzfix.js, otherwise you get an error when no
datefields exist on your page:
-snip--snip--snip--snip-
if (Tapestry.DateField != null) {
[...previous file contents...]
}
-s
Hello people,
Thanks for your fix Konstantin !
For those (like me) who are using a layout/border, I've refactored your
code in a mixin that includes the workaround javascript in a mixin
suitable for inclusion in layouts. This is a global fix that works for
datefields in beanforms.
Here's my mixi
That is right ,Thanks a lot.
2008/10/2 Jecki <[EMAIL PROTECTED]>
> On Thu, Oct 2, 2008 at 7:20 AM, Doublel <[EMAIL PROTECTED]> wrote:
> > Thank you for your fix, It can work by default. but When i user
> > t:format="/mm/dd" for dateFIeld to format the data ,it return
> > '2008/00/26' too .t
On Thu, Oct 2, 2008 at 7:20 AM, Doublel <[EMAIL PROTECTED]> wrote:
> Thank you for your fix, It can work by default. but When i user
> t:format="/mm/dd" for dateFIeld to format the data ,it return
> '2008/00/26' too .the month is always "00".
>
>
I believe the format should be "/MM/dd" a
timezones: EEST, EET. So you'll have to add your own
> too
> in datefield-tzfix.js script see attachement.
> http://www.nabble.com/file/p19756273/datefield-tzfix.js datefield-tzfix.js
> --
> View this message
ld-tzfix.js script see attachement.
http://www.nabble.com/file/p19756273/datefield-tzfix.js datefield-tzfix.js
--
View this message in context:
http://www.nabble.com/Tapestry-5.0.15-DateField-localization-problem-tp19723586p19756273.html
Sent from the Tapestry -
I encounter the same problem.
I use:
In FF explorer I choose today It return "2008/00/13".
In IE explorer I run into javascrip error 'style' is null or not an
object. and when I second choose date It return "2008/00/13". too
--
得与失都是生活
x would be changing date.toString() to date.getGMTString() -
which is deprecated long time ago.
--
View this message in context:
http://www.nabble.com/Tapestry-5.0.15-DateField-localization-problem-tp19723586p19723586.html
Sent from the Tapestry - User mailing list archive at
date field format parameter is working for 5.0.9
however, changing to a apache license compatible calendar
made that parameter temporarily unavailable in 5.0.10
browse mailing list archives for format examples
On Feb 18, 2008 10:53 AM, Steph <[EMAIL PROTECTED]> wrote:
> How do we set the format o
How do we set the format of the DateField component ?
I can't find any information or sample on that subject ...
Thanks in advance ?
14 matches
Mail list logo
