On May 25, 5:57 am, "Thor (Google Employee)" <[email protected]> wrote: > Hi Pil, > > Thanks for this list. I'll comment individually on each. It's > important to remember though that just because something was in v2 > does not mean it must automatically go into v3. There are many > features of v2 that we know received very little use, and would > therefore just bloat v3 unnecessarily. > > On May 25, 6:27 pm, Pil <[email protected]> wrote: > > > > > 1. Overview map > > Is this useful? It's no longer expanded by default on maps.google.com. > If there is demand for it we can add it. > > > 2. GHierarchicalMapTypeControl > > We're working on this. It's important for accurately reflecting the > current maps.google.com UI. > > > 3. GLayer > > We have started adding layers in v3, including layers for KML, > Traffic, Bicycling, and Fusion Tables. Instead of having a single > layer class as in v2 we are adding separate classes per layer type. > We're focusing on the layers that we feel offer the most benefit to > developers. We have also extended the layer concept in v3 such that > layers can be dynamic and applications can register listeners for > click events on layers which are passed the relevant data for the > clicked feature. This allows applications to be built that use the > data behind the layer, rather than the layer being just a fixed > overlay. > > The Wikipedia and Panoramio layers did not see much adoption in v2, so > are not currently a priority. If they are important to you let us know > on the Issue Tracker. > > > 4. distanceFrom() > > We're planning a more extensive library of spherical geometry > functions for v3, which will be an optional module, rather than just > mixing them in with the classes concerned. > > > 5. Encoded polylines > > We have not exposed polyline decoding in v3 so far because we were not > sure if encoded polylines offered much value now that v3 performs > simplification and level of detail calculation automatically for all > polylines. If it would still be useful to offer polyline decoding we > can expose it. > > > 6. XML parser (incl. GDownloadUrl, GXml, GXmlHttp) > > These functions were added to v2 back when there were very few other > JS libraries available. In truth though they are not at all maps > related and have no place in a Maps API these days when there are many > other libraries that are focused on providing generic cross browser > utility functions. Consequently we're not planning to add them to v3 > but instead recommend you consider alternatives such as Closure. > > > 7. GScreenOverlay > > We are not adding GScreenOverlay to v3 because it is confusing to > developers (all other 'overlays' move with the map) and it's function > can just as effectively be served by a custom control. > > > 8. GDraggableObject > > Again, this is not Maps specific and is better served by other > libraries. > > > 9. GGroundOverlay > > Has already been added to v3: > > http://code.google.com/apis/maps/documentation/javascript/overlays.ht... > > > 10. G_API_VERSION > > Has not been exposed until now because we did not have a versioning > scheme. Now that we have just added one we can expose the version > number if there is demand for it. However I'd like to know what the > value is?
It allows developers to know what version their map is currently using and when it changes. Very useful when things suddenly break for reporting what version works and what version doesn't. Before it existed in V2 we had to parse it out of the script being included and there were people that were doing that. -- Larry > > > 11. Maximization of info windows > > We stopped using maximised InfoWindows on maps.google.com some time > ago because they were a poor UI, so do not plan to offer this in v3. > > > 12. Tabbed info windows > > We have no plans currently to offer tabbed InfoWindows, but will > consider it if there is demand for it. Please raise this on the Issue > Tracker. > > Many thanks, > > Thor. > > > All these features are completely absent in v3. For about a half of > > them it is said they should be written by the maps programmer, so they > > will never appear in v3. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Maps API" 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 > > athttp://groups.google.com/group/google-maps-api?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API" 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 > athttp://groups.google.com/group/google-maps-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
