Toolkit Components and Product Roadmap
The Toolkit’s Contents
The Highcharts for Python Toolkit features a number of separate Python
libraries which extend the core Highcharts Core for Python
highcharts-core) library. This pattern maps quite naturally to the
The Highcharts for Python Toolkit includes two categories of tools:
These libraries correspond to each of the major Highcharts products:
These libraries serve as extensions to the core visualization libraries, providing specialized functionality to simplify usage of the Highcharts for Python Toolkit in various applications:
A number of extension libraries are in progress, but have not yet been released. Watch this space for news soon!
All extensions to the Highcharts for Python Toolkit support visualizations produced in any of the core libraries. For more information, please see Supported Visualizations.
The Toolkit’s Roadmap
There are a number of features (and in some cases complete components) slated for development. While detailed write-ups of each feature can be found in the respective project repositories, the lists below provides some high-level information.
Needed Script Tags ( #12 ). It would be helpful for Highcharts for Python to support the production of the relevant
<script/>tags needed to include the Highcharts JS modules that are needed to render a specific chart (and to not include the modules that are not needed).
In addition, this functionality should support the specification of:
custom script locations for the relevant Highcharts (JS) modules as needed
version-locking the Highcharts (JS) script versions to load
Support for Explicit Defaults ( #13 ). Currently, Highcharts default values are always presented as
Nonein outputs within Python, and are stripped from the serialized JSON or JS literal representation of all objects (because that way the Highcharts JS library applies its default). While this is valuable to minimize irrelevant data and shrink content passed along the wire, it does force developers to track / remember / understand the Highcharts defaults (which are called out in the docs, obviously - but still…it’s a pain). So in the Zen of Python spirit that “explicit is better than implicit”, there needs to be a mechanism for users to explicitly request that default values are accessible in Python and shown when serializing the chart configuration.
Styled Mode Configuration ( #14 ). While styled mode can currently be enabled in Highcharts for Python, the library does not provide for the actual definition or configuration of Highcharts CSS. It would be good if it did, so that all Highcharts-related configuration could be handled within the library.
Watch this space…we’ll be announcing some new extensions soon.
Additional Tools Needed?
Are you looking for additional tools that are not already part of the Highcharts for Python Toolkit? Drop us a note with a feature request in our Github Issues Page.