Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-09 Thread Daniel Bell
Vinay, I just created a wave at https://wave.google.com/wave/waveref/googlewave.com/w+R9B29isxA that we can use to discuss the features and plans to sync up. I've just written what I've done so far, and what I'm currently working on. Cheers, Daniel On 8 July 2010 01:35, Vinay Sekhri

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Eric Ayers
The author of that library has plans to migrate to overlay types. We've got a change branch going on http://code.google.com/p/gwt-google-apis under changes/vinays/. http://code.google.com/p/gwt-google-apis/source/browse/#svn/changes/vinays/gwt-google-maps-v3 On Tue, Jul 6, 2010 at 10:08 PM,

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Eric Ayers
Oh, and I meant to say that your contributions are welcome! On Wed, Jul 7, 2010 at 7:38 AM, Eric Ayers zun...@google.com wrote: The author of that library has plans to migrate to overlay types. We've got a change branch going on http://code.google.com/p/gwt-google-apis under changes/vinays/.

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Daniel Bell
Thanks Eric, Vinay. Which project would you prefer I contributed the code to? So far I've I've been working with a clone of the repo at gwt-google-maps-v3, but I'm happy to switch to using the gwt-google-apis branch if that will help with migration and API stability. On 7 July 2010 21:50, Vinay

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Vinay Sekhri
Daniel, I guess it would make sense for you to contribute code at gwt-google-apis vinays branch. Plan is to convert the existing JSIO dependent code to Overlay types and write test cases for the same. You may also opt to write missing types from JS API using Overlay types. Let me know what you

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Daniel Bell
Hi Vinay, That sounds good. I'll probably start with converting some of the code using JSIO to use overlay types, because that's what I'm using for my current project. Regarding testing, it seems that the tests used in the gwt-google-apis Maps v2 API use the gwt-google-apis AjaxLoader

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Eric Ayers
There are reports of success loading the v3 API with the AJAX Loader (aka Common Loader). The AjaxLoader Java support is API agnostic. You should be able to provide the same parameters to AjaxLoader.loadApi() as described in the forum post below:

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-07 Thread Daniel Bell
Thanks for the suggestions. I like the script tag injector idea. I'm currently using AjaxLoader in to load the v2 API when the user navigates to the page with the map in it. I did try the using AjaxLoader.loadApi() to get the Maps v3 API (using the same params described in the forum post you

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-06 Thread John Tamplin
On Tue, Jul 6, 2010 at 3:08 AM, Daniel Bell daniel.r.b...@gmail.com 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.

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-06 Thread Eric Ayers
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 j...@google.com wrote: On Tue, Jul 6, 2010 at 3:08 AM, Daniel Bell daniel.r.b...@gmail.com wrote: I have a question for you about Overlay Types and the JSIO

Re: [gwt-contrib] JSIO vs Overlay Types

2010-07-06 Thread Daniel Bell
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