Currently ClientProperties object has a getTimeZone() method, that uses BrowserInfoPage's response, to calculate a client's Timezone.
Would it be too much trouble to add a setTimeZone() method, so that the TimeZone property is user settable ? I can save a user's preferred timezone, in a user profile object and store that in a session. But the wicket-datetime java classes, depend on the ClientProperties.timeZone field, to properly convert dates to-&-fro between the server and client timezones. So the best place to store a user's preferred timezone seems to be the ClientProperties object . thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
