cybernytrix schrieb: > The chart dates are off and it seems you are using UTC date on the > client side (in you Javascript code). This weird and I don't > understand why you would use UTC date instead of the normal date. (...) > Please let me know if there is some obvious thing wrong doing it this > way (and why!)
Yes, actually your fix is too simple. You may want to read http://flot.googlecode.com/svn/trunk/API.txt Basically it's like this: * Javascript does not have any usable timezone handling. The only reliable timezone in Javascript is UTC. * Assumption is that the server app needs to control exactly how the chart is displayed on the web site. * If flot would not use UTC parsing, Javascript will interpret the date in the user's local timezone which is unpredictable (=> Chart will look different for every user) What we do in 0.7: We read the dates from the database in some timezone. Add the UTC offset in that timezone and hand that timestamp over to flot. The known problem here is that for people in different timezones the dates will be wrong. In 0.8 one of the main user visible features is better handling of different timezones (storing the burndown data in UTC, showing them in the timezone preferred by the user). So if burndown dates are wrong you should parse the timestamps, shift them by the timezone in your server and check if they are still wrong. Then look in the burndown chart code to find the problem. fs --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
