> This page loads almost 20 separate javascript files; it also loads a
> few dozen style sheets, including several style sheets referenced as
> src for scripts!
sorry, that's the problem with working with a higher level framework.
optimization comes next :-)
it's also why I posted a snippet above.
> I don't even see where the Maps API key is referenced, but maybe one
> of the scripts is doing that??
I recently switched to accessing google.com/jsapi directly, and that's
been working well so far.
> It's handy to have the API documentation nearby, but may I suggest
> keeping it on a separate page?
>
> For testing and learning, start with a plain map page.
>
> Ideally, also start with only the Maps API script reference.
Thanks for the suggestions. After progressing through that path, I
switched to slightly a slightly more up-to-date reference on the
google api page using the google.maps namespace, and the map works
well now.
> As fun as it would be, tracing the flow of program control among all
> of the existing scripts would be attempted only by those with powerful
> motivation!
tell me about it :-0
cheers,
nb
BTW: the map works well now. the issue turned out to be (imho) waiting
until the map markup was present (it was hidden by yui until the
dialog was displayed) to call google.load('maps', '2',
{\"other_params\":\"sensor=false\"}); and google.setOnLoadCallback
(map_initialize); to control when events ran.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
