conversion to V3 questions

[Nico Oudshoorn]

I have two questions at the moment:

1) in V2 we had GUload in the body; inV# this gives an error; has V3 an replacement for GUnload?

2) I remember that in V2 we had to insert this statement: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />; do we need this in V# or does it have a replacement?

 

[Kesuke]

1.) This guide should help explain how to call the map in V3:
http://code.google.com/apis/maps/documentation/javascript/tutorial.html

Essentially your map code will go in a javascript function, and in the
body tag you will call that function. In the 'hello world' example
over at that link you will see we usually call it initialize(); but
you could rename it to whatever you want obviously provided both the
function and the call have the same name.

You don't need to call GUnload anymore, because map assets are (in
theory at least) dynamically cleared by the browser and the API as it
goes. Its a little bit contentious, you can read more about it at this
link if you really want, or just take my word for it:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=772

2.) Per the 'hello world' example at the first link, you don't need to
include an IE7 standards mode meta-tag in V3 as far as I am aware.

[Pil]

I'd consider it possible that Micosoft realized that they were on a
blind alley with this proprietary non-standard meta tag.

<meta x-ua-compatible....

It's maybe still necessary for backwards compatibility with IE 8, but
they don't use it anymore on their own maps. So - hopefully - there
will never be a replacement, substitution or alternative for this.

If you want your maps to work properly in IE you'd have to test them
completely in IE 6, IE 7, IE 8, and IE 9 anyway.