-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saving widget state in ipynb #62
Comments
@miduncan What's the payload that is written to the notebook when using the "Save Notebook Widget State" item? |
@captainsafia It looks something like this (irrelevant fields omitted)
|
As far as not having outputs writing that in a notebook, we could possible store a reference to the Widget Manager somewhere in a redux store. Then we could make the |
Yeah, I'm not opposed to the idea on principle but I think the design needs to be fleshed out a little bit more especially because it does require some bidrectional interactions between the parent app and an individual output.
Yeah, maybe we can store a reference to the Widget manager in the transient state of the notebook. It looks like get state will serialize all the widgets in the notebook? How do we make sure that we write the correct serialized version to the output on disk? |
Jupyterlab and Jupyter-classic both support a way to save the notebook such that it persists the widget data in the ipynb (see here). This can be used so that exporting a notebooks will show the widgets with the correct value. It is done by writing to the metadata portion of the ipynb, not by changing the output value saved in the ipynb. My question is
The text was updated successfully, but these errors were encountered: