Hi Chad, We are committed to maintaining backward compatibility on all features for multiple years going forward (more communication on that forthcoming from Google in the near future) and to supporting robust, enterprise-grade applications with the API from this and other perspectives (uptimes, SLAs, etc).
The old behavior of the Table Visualization was seen by us and by external users as a buggy implementation, and therefore the fix was rolled out. With our last push of 2008 we also included a new section in the documentation containing a changelog<http://code.google.com/apis/visualization/documentation/release_notes.html>of all new features and bug fixes. This further improved our transparency to you, the developers, on our updates. We realize certain buggy behaviors may require developers to create work-arounds, and therefore, dependencies, on these bugs. Just as the case with this one. We believe we need to earn your trust as a developer. So, in addition to our commitment to backward compatibility on all features we think we need to minimize cases in which we break such "work-around dependencies" on bugs. As such, we will be enhancing the changelog section and announcing fixes to bugs prior to their pushes. Exact details of the imnplementation of that are being worked out and will be announced soon. We value your feedback and are planning more tools to help you communicate with us. Expect those too in the near future. In the meantime, we hope you continue to use the API and enjoy it. The Visualization Team On Thu, Jan 15, 2009 at 3:40 PM, Chad Morris <[email protected]> wrote: > > Hi all: > A recent update to the Table visualization broke behavior we were > relying on for event-based paging. When page is set to "event", the > paging controls will not appear unless there are more rows in the data > table than set in the pageSize option. They used to always appear, > and we used this to implement a lazy-loaded grid control, only loading > each page's records. With the new change, the paging controls would > never appear, since we always loaded into the DataTable exactly the > rows to show on the page. We were able to patch this on our end by > always adding an empty blank row to the end of our DataTable if the > page was otherwise full to force the controls to appear, but that is > not ideal. > > My larger complaint is that the visualization changed without warning > in backwards incompatible ways, which is a complete killer for using > the Visualization API for anything even remotely robust. > > Thanks, > Chad > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
