You really need indicate the manner in which you're calculating the "tomorrow date" before anyone can actually do much other than speculate to help you here.
I would imagine you should be able to determine what the code is doing differently just by stepping through your code in the browser's debugger after compiling using -style DETAILED and deploy the app locally and then compare it to the java Date calls. I'd guess there's some sort of javascript difference in date handling poking through the java abstraction.
On Friday, November 1, 2013 4:11:59 AM UTC-5, Axel R wrote:
-- I would imagine you should be able to determine what the code is doing differently just by stepping through your code in the browser's debugger after compiling using -style DETAILED and deploy the app locally and then compare it to the java Date calls. I'd guess there's some sort of javascript difference in date handling poking through the java abstraction.
On Friday, November 1, 2013 4:11:59 AM UTC-5, Axel R wrote:
Hi,Yesturday, Oct 31th, 2013, I had a bug with "gwt date" (I do not understand if the java.util.date has something to do with GWT but well...).I have an 'event application', and when I was using the gwt datepicker to go the the 2nd NOV, 2013, my application has also to calculate the date of the following day.In this example, the "tomorrow" date was indicating 3rd DEC 2013 instead of 3rd NOV 2013... (so the issue is that the date is giving me one month more).This error was in production mode. Then I try to debug it in local mode. And I can observe something strange:- with SUPER DEV MODE: I have the same error than in production.- withOUT SUPER DEV MODE (normal debug): I can see that the "tomorrow" date is OK (cf. 3rd NOV 2013)Then I go home to sleep, sooo frustrated to lose time debuging incoherent thing, and most of all, not allowing my team to update events in production due to the bug...I weak up this morning, and well, everything seems alright. I mean, the "tomorrow" date is well calculated, without a month more...So where this bug comes from ? Is it my fault or not ? I think that GWT can do great thing, but for example, or sometime, it is bad in doing simple things...Which serious EVENT / CALENDAR application could we develop without a COOL and BUGGYLESS way of maniplating dates in the client side ? Moreover, the GWT datepicker widget has bugs that have not been corrected for 3 years...I have to do some ugly hack for this. Frustating answers are talking about using JODA or Calendar, but it does not work in the client side, and in my country the internet connexion is very slow, I do not want to do an RPC just to do some date calculations each time I need it.Now, which garantee I have that the bug that happened yesturday will not happen another day ?Axel,
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment