If you were talking about Earth view or user-editable polygons, I'd be the first to agree with you.
But GXmlHttp? This has nothing to do with mapping. The only reason it was ever in the API is that the V2 API predated the popularity of libraries like jQuery, MooTools, Prototype, and you name it. These all have XMLHttpRequest wrappers built in, so it's just redundant code. There's really not much overhead involved in including jQuery in your pages these days, since you can load it from the Google Ajax Library API and many of your visitors will already have it cached. For GXml.parse(), you really ought to be using JSON instead of XML if you possibly can. It is so much simpler to work with in your JavaScript code, and just as easy to generate on most any server. If you do need an XML parser and it isn't in whatever library you use, you can steal the code from GXml.parse() like I did in this post... :-) https://groups.google.com/d/msg/jquery-en/lXGMmqssdIM/FuieiBevFTsJ -Mike On Fri, Feb 18, 2011 at 2:05 PM, SJL <la.jolie.tigresse.heure...@gmail.com>wrote: > I don't understand why they don't care about us not having the tools to do > things we could easily do before, like GXmlHttp. At worst it creates a > significant barrier towards modernizing things. At best, having to create > our own non-standard functions to replace previously included functions > partially defeats the purpose of an API. And now it's at least 2 years > later without any improvement on their part. I'm sure I'll be able to find > lots of people who managed to make things work on their own, but again that > defeats the point of an API. > > -- 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
