We are looking at porting our GWT Maps v2 apps to v3. As we understand it there are 2 principle efforts/libs to this effect:
1. http://code.google.com/p/gwt-google-maps-v3/ 2. http://code.google.com/p/gwt-google-apis/downloads/detail?name=gwt-maps-3.8.0-pre1.zip It does appear that the following issues are problematic and/or will require considerable re-engineering when going from v2 to v3: - - tabbed / composite info-windows (for polylines and markers) (they don't exist in v3) - - polyline clickhandlers (broken in v3?) - - Control clickhandlers e.g., custom Button on the map. (broken in v3?) Anyone have systematic porting experience now and willing to share a) which lib they chose, b) how they implemented tabbed infowindows containing widgets (requiring click handlers), and polyline and control clicks, and any other gotchas? There are a few examples showing case by case mitigation of issues but the code samples are limited and we're finding it a challenge thus far (e.g., overriding InfoWindow - how?). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
