Hi,
I am playing with timezones... for listGrid the following rules are valid if server timezone is different from browser timezone:
1. Date with timzone = 2017-08-13T00:00:00.000+02:00 => DateTime set be used and recalculated from GMT+2:00 to the local browser timezone (Awesome!!!)
2. Date without timzone = 2017-08-10T00:00:00.000 => Date will be set and smartGWT sets the browser timezone as timezone without any dateTime recalculation (Awesome!!!)
This is a great behaviour, because we do not need to recalulate the dates manually on the server, we simply can deliver a date with or without a timezone. The Server needs not to know the timezone of the browser.
Now if you are using the timeline... the following case appears:
1. Date with timzone = 2017-08-13T00:00:00.000+02:00 = DateTime will be set and converted from GMT+2:00 to local browser timezone (Awesome!!!)
2. Date without timzone = 2017-08-10T00:00:00.000 = DateTime will be set and converted from GMT+0:00 to local browser timezone (Not so good)
So in the timeline you can see some gaps:
This means for timelines... we need to recalulate all dates manually to the browser timezone and we will always have to add the browser timezone to date. This can be tricky if server and browser have different timezones. The Server always needs not to know the timezone of the browser.
Thanks
Andy
I am playing with timezones... for listGrid the following rules are valid if server timezone is different from browser timezone:
1. Date with timzone = 2017-08-13T00:00:00.000+02:00 => DateTime set be used and recalculated from GMT+2:00 to the local browser timezone (Awesome!!!)
2. Date without timzone = 2017-08-10T00:00:00.000 => Date will be set and smartGWT sets the browser timezone as timezone without any dateTime recalculation (Awesome!!!)
This is a great behaviour, because we do not need to recalulate the dates manually on the server, we simply can deliver a date with or without a timezone. The Server needs not to know the timezone of the browser.
Now if you are using the timeline... the following case appears:
1. Date with timzone = 2017-08-13T00:00:00.000+02:00 = DateTime will be set and converted from GMT+2:00 to local browser timezone (Awesome!!!)
2. Date without timzone = 2017-08-10T00:00:00.000 = DateTime will be set and converted from GMT+0:00 to local browser timezone (Not so good)
So in the timeline you can see some gaps:
This means for timelines... we need to recalulate all dates manually to the browser timezone and we will always have to add the browser timezone to date. This can be tricky if server and browser have different timezones. The Server always needs not to know the timezone of the browser.
Thanks
Andy