Skip to content
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

Storing widgets in notebook output #404

Closed
aiguofer opened this issue Mar 3, 2016 · 2 comments
Closed

Storing widgets in notebook output #404

aiguofer opened this issue Mar 3, 2016 · 2 comments
Labels
discussion resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@aiguofer
Copy link

aiguofer commented Mar 3, 2016

I'm not sure if this has been discussed before, but I couldn't find it. I read somewhere that widgets are persisted in browser storage, but that doesn't help this case. Maybe it's related to #16?

Anyway, I've noticed that when I create a notebook with widgets, if I share the notebook with someone they can see the output. This is great, especially when using jupyter_dashboard, but the problem is that if I want to incorporate widgets into a notebook, they would have to execute the whole notebook themselves. This makes it cumbersome when I want to share a dashboard with someone. Is there a way to make widgets persist in the output so other people have access to them?

@jdfreder
Copy link
Contributor

jdfreder commented Mar 4, 2016

Persist live widgets, no. Persist static renderings of those widgets, yes. In master, which will be released soon as ipywidgets 5.0, the widgets add a "widgets" menu which allows you to save the notebook w/ static renderings of the widgets.

@jdfreder jdfreder closed this as completed Mar 4, 2016
@jdfreder jdfreder added this to the wishlist milestone Mar 4, 2016
@aiguofer
Copy link
Author

aiguofer commented Mar 4, 2016

Ahh I see, but the static rendering wouldn't be linked to the callback in that case then?

@minrk minrk modified the milestones: No action, Backlog Nov 24, 2016
@github-actions github-actions bot added the resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Feb 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discussion resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

No branches or pull requests

3 participants