I made another tests, this time trying to get proper date and time using timezone triggers if possible. Fortunately tests went good and these are my findings.
Task 1: send client date and time without change to server
We can add various GMTs to <Time Zone> trigger in Format Date and Time model and the time will be counted as:
Local time in sent timezone,
(so NOT specifically client timezone, but any timezone we put into trigger <Time Zone>)
When Tersus Team will add features from #204 (timezone triggers to Now etc.) it will be easier to get client's timezone, but as long as we predict or know exactly what timezone client is, we can simply put his proper GMT to <Time Zone> trigger.
If on client side timezone is set properly, but user will change hours i. e. 1 hour forward, then no matter what timezone we choose, server will get time in specific timezone + 1 hour
Now Format Date and Time model returns <Text>, if someone want Date and Time type to get he can model it by himself. We did it in this way:
In those models we need to model some extra parsing using text operations.
Task 2: Send server date and time without change to client
Again we use Format Date and Time model, but we need to provide server's GMT.
Now (2009-09-15) Format Date and Time is Server side plugin only, but it changes nothing - server's date and time is properly returned :)
Tersus Team plans to create Client side plugin so it will be more efficient, but even now it works.
Additional pics and download:
I put here some result pages of my test application:
Ok that's it.
Now we'll start implementing our timezone related features in our system, so we'll know in practise if that's all we need.
For now I'd like to thanks David Davidson for all support and hope this wee "tutorial" will help someone in future.
For best results, use the Firefox browser..