Hi Guys,
I have a question for you about Overlay Types and the JSIO library.
I'm working on a GWT interface to the Google Maps JavaScript API, and
am wondering about the difference in performance between the two
approaches.
With JSIO I've been using wrapper objects that each contain an
instance of
Comment by moorsu:
Please note that the spelling of the compile flag.
It should be -XdisableClassMetadata
For more information:
http://code.google.com/p/google-web-toolkit/wiki/NoClassMetadataOptimization
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Comment by moorsu:
Please note the spelling of the compiler flag.
It should be
{{{
-XdisableClassMetadata
}}}
For more information:
http://code.google.com/p/google-web-toolkit/wiki/NoClassMetadataOptimization
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On Tue, Jul 6, 2010 at 3:08 AM, Daniel Bell wrote:
> I have a question for you about Overlay Types and the JSIO library.
> I'm working on a GWT interface to the Google Maps JavaScript API, and
> am wondering about the difference in performance between the two
> approaches.
> With JSIO I've been u
Overlay types are the way to go. The gwt-maps API use jsio because it
predates overlay types.
On Jul 6, 2010 11:18 AM, "John Tamplin" wrote:
> On Tue, Jul 6, 2010 at 3:08 AM, Daniel Bell
wrote:
>
>> I have a question for you about Overlay Types and the JSIO library.
>> I'm working on a GWT inte
Thanks for the feedback. The reason I'm not using the official Maps API is
that I need to use version 3 of the JavaScript API, which isn't supported by
the GWT Google APIs project yet. The more developed of the GWT Maps
Libraries (http://code.google.com/p/gwt-google-maps-v3/) uses JSIO for
everythi