Google API Managers: After six grueling hours of hard work trying to convert a V2 module to V3, I finally realize that there is no such thing as "mousemove" and "mouseover" on the map canvas in API V3. Wow, this really makes things hard!
I assume from reading some of the posts that Google doesn't think that folks need these handlers because they don't apply on touch screen phones. Now I think that there are some serious ambiguities about V3. Is it ONLY for phones? I thought this was the future of the API and I have been trying to get ahead of the curve by converting my work sooner rather than later. What is a developer expected to do? - use one API for computers, and a different one for mobile devices? What about the iPad? Will there be a full set of handlers? I think it should be up to the developer to know whether they are on a phone or a computer and program accordingly, but with only a single API. I can't imagine maintaining all my code in two different APIs. Google has not included a lot in API 3. I thought this was because it wasn't nearly finished. Now I think that certain things are expected to to be moved to other utility libraries like "Tabbed InfoWindows", yet how is one to know what's going where? I have been struggling to program industrial strength applications with Google Maps for real companies since 2005, from no official API, to API 1, to API 2, and now API 3. I want my code to operate on both phones and computers. Please provide some advice and guidance. Extremely disgruntled, David Coggeshall SFC MapLab Project [email protected] -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
