Google Charts New Release Candidate: V52, Feb 20, 2023

150 views
Skip to first unread message

Daniel LaLiberte

unread,
Feb 20, 2023, 2:15:59 PM2/20/23
to google-c...@googlegroups.com, Google Visualization API

Google Charts version '52' is now available.  You can use this upcoming version by loading 'upcoming'.  Please test the new features and let us know if you experience any issues.  


<script>

  google.charts.load('upcoming',

   {packages: ['corechart']});

</script>


This release primarily consists of a large number of refactoring and cleanup changes.  All code has been migrated to ES6, and a substantial fraction has been migrated to TypeScript. We are still moving forward toward open-sourcing the Google Charts code, but many more internal changes are required before that can be accomplished.



Anticipated production release date: March 20, 2023

At this time, the 'current' version is still '51'.

On the release date, loading either 'current' or 'upcoming' will load '52'. 


Note that this is a much longer release cycle compared to previous releases, due to the large number of internal changes.



  • GeoChart

    • Updated geochartVersion to 11, and regioncoderVersion to 1.

  • Dygraph charts

    • Gantt, Timeline, and the Material charts: Bar, Line, Scatter

    • No longer loads the Dygraph library dynamically since it is compiled in.

  • Table

    • Fix highlighting of current page number for more than 11 pages.

  • OrgChart

    • Add ‘compactRows’ option. Default is false.

    • Uses the  Reingold-Tilford algorithm for layered trees. Its main advantage is a more effective use of horizontal space by placing subtrees close together as long as nodes in the same layer do not overlap.


--

Daniel LaLiberte

 • SWE

 Cambridge MA

 • dlaliberte@Google.com

Daniel LaLiberte

unread,
Feb 21, 2023, 6:05:36 PM2/21/23
to google-c...@googlegroups.com, Google Visualization API
If you are using both Google Charts and Google Maps in the same document, you might have a problem using the 'upcoming' version.

I am seeing a single instance of "var google = {};" in the default package of v52, which is loaded before any other package, or even if no other package is loaded.  Consequently, any previously loaded google.maps code will be deleted. Until I figure this out, this probably means that anyone using both Google Charts and Google Maps in the same document cannot load the 'upcoming' version. Alternatively, if 'upcoming' is required, it might work to load the Google Charts code before loading the Google Maps code. 

Daniel LaLiberte

unread,
Mar 11, 2023, 5:37:51 PM3/11/23
to gviz-users, Daniel LaLiberte, google-c...@googlegroups.com
I've updated v52 with a fix for the orgchart bug (when the table would have colspans greater than 1000).  There are also a large number of changes to the module structure of the code, all to eliminate the "var google = {}" problem.  But there should be no change of behavior otherwise.

Given the number of changes, I'll extend the testing period before production release by another week, to March 27.
Reply all
Reply to author
Forward
0 new messages