v2: Add VegaFusionWidget based on AnyWidget #514
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new implementation of VegaFusionWidget (the original was removed with the removal of the
vegafusion-jupyterpackage) based on AnyWidget. This implementation is heavily based on the JupyterChart implementation I did for Altair. It uses the ChartState approach for managing state and inline datasets in Python so that it's not neccesary to write datasets to disk, or to compile VegaFusion to wasm to run in the browser.This widget supports only Vega specs, not Vega-Lite. For Vega-Lite the recommendation is the either convert to Vega with vl-convert, or convert to an Altair chart and use JupyterChart.