I was really shocked about this discovery myself. I spent hours this morning trying to find a list of version numbers to pass into the load method. It really puts us as developers at the mercy of major bugs. Right now no charts are working for Firefox. I am scrambling to find a solution. There should be a way when we release our software to say "this is version 1.1.0" and in our next release, we move up to the latest API version. It puts the developers back in control.
As much as I love Gviz, this is a serious issue. On Tuesday, April 3, 2012 11:07:22 PM UTC-4, NA wrote: > > > I have a slightly different question: > > Why hasn't the GVIZ team add versioning consistent with what's in other > products? > > Please don't reply saying "we will consider it". That's not what I'm > asking for. I am specifically asking why you haven't added it yet despite > requests to do so for at least 2 yrs. Not doing so contradicts what Google > does with other services and possibly with Google's Deprecation Policy > (which agrees to use commercially reasonable efforts to support deprecated > versions). > > There must be a good reason for not implementing versioning. > Understanding that reason would really help your external users understand > the product better. > > Can someone from Google give a thoughtful response to this? I'd really > appreciate it, as would many of us on the group here. > > thanks, > > > > > -- 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/-/1q-8mw_j6WcJ. 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-visualization-api?hl=en.
