John, A google hosted service would be great, sounds like a good, valuable service, of use to everyone on the web. I don't mind asynchronously fetching this data, because you typically have to ask the user which TZ he's in anyway, unless you try to infer it from the browser's Date.toString() method, which isn't always reliable. (Some browsers report actual TZ Common names, others don't)
-Ray On Fri, Apr 3, 2009 at 4:34 PM, John Tamplin <j...@google.com> wrote: > On Fri, Apr 3, 2009 at 7:28 PM, Ray Cromwell <cromwell...@gmail.com>wrote: > >> >> Am I missing something? There doesn't appear to be a way to query for all >> of the supported Common Timezones, which makes it problematic to construct a >> UI dialog that asks the user to specify a TimeZone without hard coding. >> Simple Timezones have the problem that they don't provide DST information, >> which makes the behavior of DateTimeFormat wrong in some TZs. I'm wondering >> if it makes sense to either 1) provide a default RPC service for obtaining >> TZ related info (localized), or revisit the issue of providing full TZ >> introspection using code splitting to reduce some of the inefficiency. >> > > Work is in progress to provide a JSONP service, either provided by Google > or where you can run a servlet on your own infrastructure, and fetch the > timezone data that way. It is too large in its current form to include in > the compiled output (though we may be able to improve that for certain > common cases in the future) and the async nature of the interface means it > won't be transparent to user code, but it should be out for review shortly. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
