Author Archive

JavaScript Versioning

4:40 pm - December 5, 2005 in Google Maps API Official Blog

Posted by Rachel Goldman, Software Engineer

Don't be caught off guard when we push a new release: the new JavaScript versioning feature has arrived, and it will mean a couple of changes for you.

You can specify previous JavaScript versions in the URL as part of the "v" parameter. In the past, the v=1 part of the URL http://maps.google.com/maps?file=api&v=1 referred to "version 1" of the API. We have updated this so that v=1.27a refers to "version 1" of the API and "version 27a" of the JavaScript. If no JavaScript file version is specified, then we use the current API default. If you want to specify earlier versions, that's OK with us, but we don't plan to support them or guarantee they will always be available.
When we push a new release, we will start serving the previous week's JavaScript to API developers by default so that everyone has at least 5 days to check compatibility before the most current version becomes the default. For example, this week Google Maps will begin using JavaScript version 28, and the Maps API will use version 27a by default. You can test version 28 by specifying v=1.28 in the URL given in the script tag. Using the letter "x" instead of a JavaScript version number, i.e., v=1.x, will cause the current release to be used immediately rather than waiting 5 days.

These changes will be effective starting with the release going out today. (The other changes we're making in the current release are minor and should have no impact on the API.) We will include the default versions in our blog post for each release. This week's versions are:

Current Release: 1.28
API Default: 1.27a

As always, we value your feedback. Feel free to post comments on the API discussion group as we'd love to hear from you.

(Navigation)
(Content start)

New JavaScript version 1.30

6:37 pm - December 21, 2005 in Google Maps API Official Blog

Posted by Rachel Goldman, Software Engineer

We will be pushing a new release today with a change to fix the positioning of info windows on our site. This change should not impact the behavior of the API. The Maps JavaScript version will be updated to 1.30 for Google Local/Maps, but the default will remain at 1.28 for the Google Maps API.

We value your feedback, so please let us know if you encounter any unintended changes to the API.

Current Release: 1.30

API Default: 1.28

(Navigation)
(Content start)

JavaScript temporarily forked

12:43 pm - January 3, 2006 in Google Maps API Official Blog

Posted by Rachel Goldman, Software Engineer

Some of you may have noticed that we have forked local.google.com to use different JavaScript from the version that's currently available in the Maps API. We're testing some new performance improvements and workarounds for browser bugs that cause memory leaks. Once these changes have been fine-tuned, we'll merge them into the Maps API JavaScript.

API Default: 1.30a

(Navigation)
(Content start)

Update on the upcoming API v2

3:05 pm - February 3, 2006 in Google Maps API Official Blog

Posted by Steffen Meschkat, Software Engineer

Note: API v1 is not affected by this update at all.

We've released revision 2.36 of the API v2. The new revision makes the upcoming API v2 backwards compatible with v1. That is, the interface of a GMap object and all the auxiliary objects is no longer different from the published API interface, with the exception of the method openInfoWindowXslt(), which we abandoned. (More on XSLT support in later posts). In order to try and explore the API v2, you need to instantiate the new class GMap2. As with v1, the current revision is available using the URL parameter v=2.x. The value v=2 will give you last week's revision.

Please be aware that the API v2 is still in alpha status, and we don't yet recommend its use.

API Default: 1.30a
API v2 Current: 2.36
API v2 Default: 2.35

(Navigation)
(Content start)

Another update on the upcoming API v2

3:06 pm - February 13, 2006 in Google Maps API Official Blog

Posted by Steffen Meschkat, Software Engineer

Note: API v1 is still not affected by this update.

We have released version 2.37 of the API v2, which means that last week's version 2.36 has now become the default version for pages that use the API v2. Notice that from this version on, the GMap behaves as it did in API v1. In order to use the API v2 methods that were available on the GMap object until version 2.35, you have to replace GMap by GMap2 in your pages.

API Default: 1.30a
API v2 Current: 2.37
API v2 Default: 2.36

(Navigation)
(Content start)

Revision 2.38 of API v2

5:59 pm - February 21, 2006 in Google Maps API Official Blog

Posted by Rachel Goldman, Software Engineer

With the release of revision 2.38 of API v2 it is now possible to test the API v2 default version with v=2. The current revision of API v2 is still available using v=2.x.

We value your feedback, so please let us know if you encounter any problems when testing API v2.

API Default: 1.30a
API v2 Current: 2.38
API v2 Default: 2.37

(Navigation)
(Content start)

Revision 2.40 of API v2

7:57 pm - March 6, 2006 in Google Maps API Official Blog

Posted by Rachel Goldman, Software Engineer

We are releasing revision 2.40 of API v2. The changes in the current revision should not affect the API. Please continue to test the alpha version of API v2 and report any problems on the Maps API discussion group.

API Default: 1.30a
API v2 Current: 2.40
API v2 Default: 2.39

(Navigation)
(Content start)

Revision 2.41 of API v2

2:48 pm - March 10, 2006 in Google Maps API Official Blog

Posted by Doug Ricket, Software Engineer

Hello Map fans! This week's revision 2.41 has no official changes, but a few intrepid users already noticed the introduction of GOverviewMapControl, which is still in alpha and under development. As always, feedback is welcome. Some initial discussion of the overview map can be found on the Google Maps API discussion group.

API Default: 1.30a
API v2 Current: 2.41
API v2 Default: 2.40