A new release candidate was pushed to 1.1

[Jinji]

Release candidate 31.1 of the Google Visualization API was pushed to 1.1 yesterday.

Planned release date: 4-Jun

Enjoy

[Jinji]

Note that this version will flip the default value of the forceIFrame option (corecharts, GeoChart, TreeMap, Gauge) from true to false. If you relied on the existence of the iframe, we especially recommend testing your code with the release candidate, and also take into account the existence  of the iframe is considered an implementation detail, and we might remove this option completely in the future.

[Sean Power]

Where can I view release candidates and how can I sign up to be notified via email?  We decided to build our site's visualizations on Google's framework, so I'd like to test release candidates and not sure how to do it.

S

[Jérôme]

Load your viz API with 1.1 parameter instead of 1 (to test the RC when there is one around) and get notification emails from this group (to know when updates are planned)

[Jinji]

If you find this group too noisy, you can subscribe to the google-chart-tools-announcements group, which is only for such announcements (which reminds me I didn't send this notification to that list. My bad. Fixing now)

On Sun, May 27, 2012 at 9:40 PM, Jérôme <jerome.b...@gmail.com> wrote:

Load your viz API with 1.1 parameter instead of 1 (to test the RC when there is one around) and get notification emails from this group (to know when updates are planned)

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/NGvAE-R_qr0J.

To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

[Andrea Dawkins]

Yuval,

I had the set the api load option to "1.x" because my GWT wrapped google visualizations stopped showing up in FireFox.  This update must have broken it again.  I am trying to get to the bottom of it, the root cause.  Where can I find the forceIframe boolean, and how does that effect the output?  Is there a canvas option instead?

Thanks,

Andrea

On Thursday, May 24, 2012 11:06:40 AM UTC-4, Yuval Ronen wrote:

[asgallant]

forceIFrame is a chart option.  Previously, most charts were drawn inside iFrames, the new standard is to not use iFrames.  Set this option to true to force the charts to draw inside an iFrame.

[Jinji]

I don't understand. Are your charts broken in 1.0 or 1.1 or both? Does changing the value of forceIFrame fixes it? Please let us know if we have a bug in 1.1, so we could fix it before the release candidate is released to stable.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/RQuXZ6ETD7MJ.

[Andrea Dawkins]

Thanks for the reply!

Charts were working fine -- I passed the loader version "1.x".  This week, the charts disappeared again.  I assume because of some change on Google's part, since our code didn't change.  Thankfully, I found this thread and your comment.  I tried setting forceIFrame = false directly, and now it works!  If forceIFrame is set to true, it won't work at all on FireFox for either 1.0 or 1.1.

I am using the GWT wrapper for the google visualizations api.  

I am very impressed with google visualizations, but I want to express my concern over the fact the code can change out from under a stable release of the software that uses it.  I understand the terms for requiring the library to be downloaded each time.  However, if I can't rely on a consistent version, it is a PR risk.  Can I ask why version numbers aren't used to version the library?  It is strange to even call it a version number if it just gets replaced with newer versions.  If there was a new number each release, developers could sync their own releases with a specific api release to ensure consistent behavior and no regressions.

To post to this group, send email to google-visualization-api@googlegroups.com.
To unsubscribe from this group, send email to google-visualization-api+unsub...@googlegroups.com.

To post to this group, send email to google-visualization-api@googlegroups.com.
To unsubscribe from this group, send email to google-visualization-api+unsub...@googlegroups.com.

[Jinji]

On Thu, May 31, 2012 at 8:07 PM, Andrea Dawkins <andi...@gmail.com> wrote:

Thanks for the reply!

Charts were working fine -- I passed the loader version "1.x".  

As far as I understand, "1.x" is a synonym for "1.1", so you were always using the latest release candidate, and not the latest stable version.

This week, the charts disappeared again.  I assume because of some change on Google's part, since our code didn't change.  

Probably, yes.

Thankfully, I found this thread and your comment.  

You're encouraged to subscribe to either group or the google-chart-tools-announcements group, where new releases (and release candidates) are announced.

I tried setting forceIFrame = false directly, and now it works!  

It's weird that setting forceIFrame = false solved your problem, since in 1.1 that's the default value of forceIFrame. I'm confused...

If forceIFrame is set to true, it won't work at all on FireFox for either 1.0 or 1.1.

I tried forceIFrame = true on firefox with both version 1.0 and 1.1, and it worked. Can you provide more details as to which chart you're using, and with what options? Best if you could make a simple HTML the reproduces the problem (preferably in Javascript, not GWT).

I am using the GWT wrapper for the google visualizations api.  

I am very impressed with google visualizations, but I want to express my concern over the fact the code can change out from under a stable release of the software that uses it.  I understand the terms for requiring the library to be downloaded each time.  However, if I can't rely on a consistent version, it is a PR risk.  Can I ask why version numbers aren't used to version the library?  It is strange to even call it a version number if it just gets replaced with newer versions.  If there was a new number each release, developers could sync their own releases with a specific api release to ensure consistent behavior and no regressions.

This is a long standing issue. Providing fixed version has many drawbacks, and we still couldn't make it work well.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/dooAMguXQlcJ.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.

[Jinji]

On Thu, May 31, 2012 at 8:45 PM, Jinji <ji...@google.com> wrote:

On Thu, May 31, 2012 at 8:07 PM, Andrea Dawkins <andi...@gmail.com> wrote:

Thanks for the reply!

Charts were working fine -- I passed the loader version "1.x".  

As far as I understand, "1.x" is a synonym for "1.1", so you were always using the latest release candidate, and not the latest stable version.

This week, the charts disappeared again.  I assume because of some change on Google's part, since our code didn't change.  

Probably, yes.

Thankfully, I found this thread and your comment.  

You're encouraged to subscribe to either group or the google-chart-tools-announcements group, where new releases (and release candidates) are announced.

...to either this group or...

[Andrea Dawkins]

On Thursday, May 31, 2012 1:45:38 PM UTC-4, Yuval Ronen wrote:

As far as I understand, "1.x" is a synonym for "1.1", so you were always using the latest release candidate, and not the latest stable version.

The only explanation I can surmise is that the loader gave me a variation other than 1.1.  I found the 1.x piece of advice somewhere buried in these messages awhile back.  Other than that, I'm not sure.

 

You're encouraged to subscribe to either group or the google-chart-tools-announcements group, where new releases (and release candidates) are announced. 

Good idea!  I will definitely subscribe.  However, the latest knowledge won't help our already released software versions in the field.

It's weird that setting forceIFrame = false solved your problem, since in 1.1 that's the default value of forceIFrame. I'm confused...

I agree, weird...  Whatever the explanation, it is working now with that boolean set explicitly on the options.

 This is a long standing issue. Providing fixed version has many drawbacks, and we still couldn't make it work well.

I understand.  I hope this is still on your roadmap, because it has definite implications in the field. I realize this error was something special about my implementation, but it worked before... it would be nice to have a controlled release so something doesn't suddenly break on us. :)

Thanks again for your quick responses.

 

On Thursday, May 31, 2012 12:55:09 PM UTC-4, Yuval Ronen wrote:

I don't understand. Are your charts broken in 1.0 or 1.1 or both? Does changing the value of forceIFrame fixes it? Please let us know if we have a bug in 1.1, so we could fix it before the release candidate is released to stable.

On Thu, May 31, 2012 at 5:56 PM, asgallant <drew_g...@abtassoc.com> wrote:

forceIFrame is a chart option.  Previously, most charts were drawn inside iFrames, the new standard is to not use iFrames.  Set this option to true to force the charts to draw inside an iFrame.

On Thursday, May 31, 2012 10:45:15 AM UTC-4, Andrea Dawkins wrote:

Yuval,

I had the set the api load option to "1.x" because my GWT wrapped google visualizations stopped showing up in FireFox.  This update must have broken it again.  I am trying to get to the bottom of it, the root cause.  Where can I find the forceIframe boolean, and how does that effect the output?  Is there a canvas option instead?

Thanks,

Andrea

On Thursday, May 24, 2012 11:06:40 AM UTC-4, Yuval Ronen wrote:

Note that this version will flip the default value of the forceIFrame option (corecharts, GeoChart, TreeMap, Gauge) from true to false. If you relied on the existence of the iframe, we especially recommend testing your code with the release candidate, and also take into account the existence  of the iframe is considered an implementation detail, and we might remove this option completely in the future.

On Thu, May 24, 2012 at 11:38 AM, Jinji <ji...@google.com> wrote:

Release candidate 31.1 of the Google Visualization API was pushed to 1.1 yesterday.

Planned release date: 4-Jun

Enjoy

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/RQuXZ6ETD7MJ.

To post to this group, send email to google-visualization-api@googlegroups.com.

To unsubscribe from this group, send email to google-visualization-api+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

On Thursday, May 31, 2012 12:55:09 PM UTC-4, Yuval Ronen wrote:

I don't understand. Are your charts broken in 1.0 or 1.1 or both? Does changing the value of forceIFrame fixes it? Please let us know if we have a bug in 1.1, so we could fix it before the release candidate is released to stable.

On Thu, May 31, 2012 at 5:56 PM, asgallant <drew_g...@abtassoc.com> wrote:

forceIFrame is a chart option.  Previously, most charts were drawn inside iFrames, the new standard is to not use iFrames.  Set this option to true to force the charts to draw inside an iFrame.

On Thursday, May 31, 2012 10:45:15 AM UTC-4, Andrea Dawkins wrote:

Yuval,

I had the set the api load option to "1.x" because my GWT wrapped google visualizations stopped showing up in FireFox.  This update must have broken it again.  I am trying to get to the bottom of it, the root cause.  Where can I find the forceIframe boolean, and how does that effect the output?  Is there a canvas option instead?

Thanks,

Andrea

On Thursday, May 24, 2012 11:06:40 AM UTC-4, Yuval Ronen wrote:

Note that this version will flip the default value of the forceIFrame option (corecharts, GeoChart, TreeMap, Gauge) from true to false. If you relied on the existence of the iframe, we especially recommend testing your code with the release candidate, and also take into account the existence  of the iframe is considered an implementation detail, and we might remove this option completely in the future.

On Thu, May 24, 2012 at 11:38 AM, Jinji <ji...@google.com> wrote:

Release candidate 31.1 of the Google Visualization API was pushed to 1.1 yesterday.

Planned release date: 4-Jun

Enjoy

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/RQuXZ6ETD7MJ.

To post to this group, send email to google-visualization-api@googlegroups.com.

To unsubscribe from this group, send email to google-visualization-api+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/dooAMguXQlcJ.

[Jinji]

OK, I've done more digging, and here are my findings:

I was wrong to say that 1.x is the same as 1.1 (and you were right to suggest that). 1.x is neither 1.0 nor 1.1. It's a third, hidden version. This version, BTW, is part of our effort to provide fixed versions, but that's besides the point. Last week we made a change to that hidden version, and that change contains a bug that manifests only if all of the following 3 conditions are met:

- Use Firefox (and I'm not sure if this includes FF12; it's possible the bug only manifest on FF11 and below. Are you still on FF11?)

- forceIFrame is true (which is the default in that version, so you don't have to do anything to meet this condition)

- Call chart.draw() at least twice without waiting for the 'ready' event in between

So I assume this what happened for you. This bug also effects 1.0 and 1.1 today. I'll fix the bug, but the fix will go live only in the next version (not even the current release candidate). In general, we recommend the following:

- Don't use 1.x. Use only 1.0 or 1.1, as documented for the Google Visualization API.

- Don't rely on explicitly setting the forceIFrame option in the long term. It's undocumented, and we may remove it completely in the future.

Given all that, I can recommend you implement one of the following:

- Wait for the 'ready' event between draw() calls.

- Load version 1.1 for now, and change to 1.0 when the current release candidate will become stable. No need to explicitly set forceIFrame.

- Explicitly set forceIFrame to false for now, and remove it when the current release candidate will become stable. Always load version 1.0.

Hope this helps.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/DUboUEUjGDIJ.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.