[Google Maps API v3] FYI: New Release (2010/05/11)

[Susannah (Google Employee)]

We have just released a new version of the JS v3 API. If there are no
major issues, we will make a full announcement of this release in
24-48 hours. Please report in the group if you see any regression
issues.

Thanks,
Susannah

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Wayne]

On May 11, 7:43 pm, "Susannah (Google Employee)"

<susann...@google.com> wrote:
> We have just released a new version of the JS v3 API. If there are no
> major issues, we will make a full announcement of this release in
> 24-48 hours. Please report in the group if you see any regression
> issues.
>
> Thanks,
> Susannah
>

The MarkerCluster demo at
http://google-maps-utility-library-v3.googlecode.com/svn/tags/markerclusterer/1.0/examples/advanced_example.html
throws a 'this.projection' is null or not an object error. This error
was
not produced prior to the API v3 new release.

Wayne

[Wayne]

> Susannah said:
> We have just released a new version of the JS v3 API. If there are no
> major issues, we will make a full announcement of this release in
> 24-48 hours. Please report in the group if you see any regression
> issues.

Hi Susannah,

[Susannah (Google Employee)]

Hi Wayne,

Thanks for reporting the error. It turns out this is an error in the
demo, where we are accessing the custom overlay's projection as
this.projection instead of this.getProjection(). We'll get the demo
fixed in the morning.

Thanks,
Susannah

On May 11, 9:42 pm, Wayne <wejans...@gmail.com> wrote:
> > Susannah said:
> > We have just released a new version of the JS v3 API. If there are no
> > major issues, we will make a full announcement of this release in
> > 24-48 hours. Please report in the group if you see any regression
> > issues.
>
> Hi Susannah,
>

> The MarkerCluster demo athttp://google-maps-utility-library-v3.googlecode.com/svn/tags/markerc...

[Luke Mahé]

Hey guys,

I've fixed the bug in the MarkerClusterer.

- Luke

[lucian.jp]

With an api v2 and an api v3 on the same page (v3 declared before v2)
before the update everything was working correctly, now I get a
javascript error with map.fitBounds(bounds) in my code with the map v3
object. Removing the api v2 make the code work, but prior to the
update it was working.

I also encounter the problem with markerClusterer and hope it will be
fixed asap. The next morning for you is quite the end of the day for
us in Europe and mean a full day with non working development code.

Thanks
--
JP

[lucian.jp]

We have a problem on page where there is api v2 and v3 on the same
page (api v3 being declared before the api v2 script). Prior to the
update it was working correctly, but now we get an error with
map.fitBounds(bounds) with the map api v3 object. Removing the api v2
script from the page fix the error, but have the side effect of
removing all our v2 map =(

On a side note we also encounter the MarkerClusterer problem. A fix in
the morning for you guys mean a fix at the end of the day in Europe
and mean a full day of non working development code. We are aware v3
is still in beta, but it's the third time there is an update breaking
things in previously working code. Is there a url parameter for the
api v3 script to force a version to stck with v3.39 instead of 3.41
for us to be able to work in the wait of a fix? (markerclusterer is an
easy one, but it migth be useful for future update.

Thanks
--
JP

On 12 mai, 04:43, "Susannah (Google Employee)" <susann...@google.com>
wrote:

[lucian.jp]

(third time I post, message aren't showing in the group, sry for the
repost if it appear in batch later)

We have a problem on page where there is api v2 and v3 on the same
page (api v3 being declared before the api v2 script). Prior to the
update it was working correctly, but now we get an error with
map.fitBounds(bounds) with the map api v3 object. Removing the api v2
script from the page fix the error, but have the side effect of
removing all our v2 map =(

On a side note we also encounter the MarkerClusterer problem. A fix in
the morning for you guys mean a fix at the end of the day in Europe
and mean a full day of non working development code. We are aware v3
is still in beta, but it's the third time there is an update breaking
things in previously working code. Is there a url parameter for the
api v3 script to force a version to stck with v3.39 instead of 3.41
for us to be able to work in the wait of a fix? (markerclusterer is an
easy one, but it migth be useful for future update.

Thanks
--
JP

On 12 mai, 07:30, "Susannah (Google Employee)" <susann...@google.com>
wrote:

> For more options, visit this group athttp://groups.google.com/group/google-maps-js-api-v3?hl=en.- Masquer le texte des messages précédents -
>
> - Afficher le texte des messages précédents -

[Nick Smith]

Any chance of making a 'more stable' version of v3 available, like
there is for API v2 ? Even if it was just delayed by a couple of
weeks, that would be enough to catch most serious issues, and it would
mean we could develop without being exposed to the bleeding edge
version, if that was what we wanted.

(The issue with MarkerClusterer had me tearing my hair out for a
couple of hours before I realised there was a new version of v3 that
was causing the problems!)

Many thanks

[Ben Appleton]

Definitely - stay tuned.

On 13 May 2010 07:28, "Nick Smith" <nickco...@googlemail.com> wrote:

Any chance of making a 'more stable' version of v3 available, like
there is for API v2 ? Even if it was just delayed by a couple of
weeks, that would be enough to catch most serious issues, and it would
mean we could develop without being exposed to the bleeding edge
version, if that was what we wanted.

(The issue with MarkerClusterer had me tearing my hair out for a
couple of hours before I realised there was a new version of v3 that
was causing the problems!)

Many thanks

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScri...

[Thor (Google Employee)]

We've deliberately chosen not to implement a versioning scheme in v3
while it is in Code Labs, because we want as many users as possible
banging on the latest version so that bugs are identified quickly, and
we want to avoid being required to maintain interfaces we need to
change any longer than necessary.

We recognise that we'll need a versioning scheme once the API has
matured to the point we are happy blessing v3 for use in change
sensitive environments (like Enterprise sites) and are working out the
details, but for the time being we'd like to stay light on our feet.

As Ben says, we'll be sure to announce when versioning is in place on
this group, so stay tuned.

Thor.

[William]

On May 12, 12:43 pm, "Susannah (Google Employee)"

<susann...@google.com> wrote:
> We have just released a new version of the JS v3 API. If there are no
> major issues, we will make a full announcement of this release in
> 24-48 hours. Please report in the group if you see any regression
> issues.
>

I've noticed a problem with the V3 KmlLayer where the InfoWindow isn't
opened on the correct anchor point on a marker. V2 GGeoXml will open
on the top center of the marker icon, but V3 KmlLayer opens on the
bottom center of the marker icon.

V2
http://code.google.com/apis/maps/documentation/examples/geoxml-rss.html

V3
http://code.google.com/apis/maps/documentation/v3/examples/layer-georss.html

...

[Ben Appleton]

Thanks for the report, we're looking into it.

- Ben