##Timezone Library for use in WebDSL projects WebDSL interprets Date/DateTime objects as if there is only one timezone: the default JVM timezone (typically the timezone of the host machine). This elib will override the Date(Time) input and output templates, and allows displaying the dates in a given timezone.
These templates make use of a global function getViewTimeZone(e : Entity), which you need to implement.
The entity e passed to getViewTimeZone(e) is the owning entity of the Date(Time) property which the input/output template
is called with. This entity can be used to derive the timezone from, but that depends on the app code. It's
recommended to set the timezone once per request and return this timezone by getViewTimeZone(e) if the app context allows this.
- Timezones can be identified with their id (String). The template
inputTimeZone( prop : Ref String )allows the selection of a timezone from a list and stores the timezone id in the givenprop. TimeZone.getTimeZone( id ): Gets the TimeZone object for the given timezone id.tz.getID(): get the id from a given TimeZone object tz.tz.getDisplayName(): get the display name of a TimeZone object tz.output(tz : TimeZone): renders the display name of a TimeZone object.d.toLocalTime(tz): get a Date(Time) object projected in the given TimeZone tz from a Date(Time) object d which was based on the default JVM timezone. E.g, to display a persisted DateTime object in a different timezone than the serverd.toServerTime(tz): get a Date(Time) object projected in default JVM timezone ( given TimeZone tz from a Date(Time) object d which was based on the default JVM timezone: , i.e. when the value is to be persistedTimeZoneUtil.getServerTimeZone(): get the TimeZone object of the server, i.e. the default JVM TimeZone.
Note: No refactoring is needed for cases where the default input and output templates are used. However, cases where date.format("some format") is used, one need to rewrite these to date.toLocalTime( tz ).format("some format").