In my opinion, having all google constants and such in a seperate namespace is quite a lot better. It removed any compatibility problems with other script or your own scripts. The only problem at the moment is that google also loads the global vars when using the ajax api. So at the moment there isn't much difference.
Please star the following issue for real namespaces: http://code.google.com/p/gmaps-api-issues/issues/detail?id=820&q=namespace&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal 2008/11/7 Mike Williams <[EMAIL PROTECTED]> > > If your page always displays a map, then I don't think there's any > advantage. > > If you've got a page on which there usually isn't a map, but there's an > optional map that the user can choose to display, then using the jsapi > loader means that you don't need to load the Maps API code until the > user chooses that option. That means that your page loads faster when > the map is not required. > > -- > http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team > > > > > -- Bjorn Brala ---------------- GeoStart.nl- Google maps - Swis Webdesign --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
