I can not imagine a more clear example of why Viz should use Google's library version scheme!
Please let ME choose when to change from version 1 to version 2, and if I am depending on bugs or ambiguity on version 1 please let me try version 2 out in my dev environment, fix my code, commit it, QA it, and ship it out to production. I know I will upgrade sooner or later because I want bug fixes and new features, but a page that specifies Visualization Version 1.2.3 should NEVER break because of a change to the viz library, even if it relies on a bug that is fixed in Version 1.2.4! The google loader knows how to do this. It understands requesting a specific revision, latest stable or latest development versions. http://code.google.com/apis/loader/#versioning On Sep 8, 4:16 am, ChartALot <[email protected]> wrote: > We have pushed a new release candidate (RC). > > > > This RC is mainly aimed at bug fixes. Please pay special attention to the > warning bellow, as we drop / change our support for some undocumented > data-table structures. > > Moreover, we created a new mailing list, > google-chart-tools-announcements<http://groups.google.com/group/google-chart-tools-announcements/subsc...>, > which will be used only for announcements such as that. > > *Candidate release date:* September 7 > > > *Anticipated production release date:* September 14 > > If your system uses the Interactive Charts in Google Chart Tools > (Visualization API) for commercial and / or important production purposes we > recommend you test the RC and use the opportunity to provide feedback to us > prior to the production release. If there are any issues, these can be > communicated back to our team by replying to this message. > > The Google Chart Tools team. > -------------------------------------------- > > WARNING: YOUR CHARTS MIGHT BREAK! > > If you are using corechart charts with data tables whose first column is of > type data/datetime/timeofday, your charts might break. Such data tables were > never supported neither documented. We're now in the process of formally > supporting them in the upcoming release, so we changed how they are handled: > > - For the charts listed below, you MUST NOT use such data tables. Doing > so will result in an error message. The type of the first column MUST be > 'string', as documented. You can convert an incompliant data table to a > compliant data table by using a DataView that converts the first column to > a > string. > Seehere<http://code.google.com/apis/chart/interactive/docs/reference.html#Dat...>. > For example, pass {calc: function(data, row) { return > data.getFormattedValue(row, 0); }, type:'string'} to > DataView.setColumns(). > - PieChart > - BarChart > - ColumnChart > - CandlestickChart > - ComboChart where some of its series are of type 'bars' > - For the charts listed below, you MAY use such data tables, but the > chart behavior in these cases changes. If you're not fond of the new > behavior, you can return to the old behavior by using the above technique > to > convert the type of first data table column to 'string'. > - LineChart > - AreaChart > - ComboChart whose all series are of type 'line' or 'area' > > You're strongly encouraged to test your charts with version 1.1 (RC) and > change your code if necessary. -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. 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.
