On Fri, Nov 7, 2008 at 1:38 PM, Mike Williams <[EMAIL PROTECTED]> wrote: > > If your page always displays a map, then I don't think there's any > advantage.
The main advantage to me is if you are using other AJAX APIs then loading via the common loader is usually easier as you already have it. And might even be quicker - not sure. Also via the the common loader you get access to 'clientLocation' which can be useful in Map terms :) > > 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. Thats not strictly true, you can load the normal API 'on demand' http://www.nearby.org.uk/google/static3.php > > -- > http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team > > > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
