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

Decouple the widgets from the Notebook. #13

Closed
jdfreder opened this issue May 5, 2015 · 8 comments · Fixed by #193
Closed

Decouple the widgets from the Notebook. #13

jdfreder opened this issue May 5, 2015 · 8 comments · Fixed by #193
Labels
proposal resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@jdfreder
Copy link
Contributor

jdfreder commented May 5, 2015

Decoupling the widgets from the Notebook should make it easier for people to embed the widgets in their own non-notebook environment. For example, @rgbkrk has already expressed interest in doing this with his BitJet widget and Sidecar app.

This means splitting the WidgetManager into a WidgetManager or WidgetManagerBase (depending on whether or not it can be used without being inherited) and a NotebookWidgetManager.

We also may want to think about the installation a little more carefully, which we will have to do soon anyways. Users may want to install (A) for use with the notebook (B) for standalone use. If @SylvainCorlay 's proposal for kernel resource/extensions is implemented, (A) is instead to a specific kernel, not the notebook.

@rgbkrk
Copy link
Contributor

rgbkrk commented May 5, 2015

👍 to kernel resource extensions and this overall issue

@rgbkrk
Copy link
Contributor

rgbkrk commented May 5, 2015

This probably also means allowing Spyder to have a display area that could have widgets.

@rgbkrk
Copy link
Contributor

rgbkrk commented Jun 16, 2015

/cc @Karissa @willwhitney

@willwhitney
Copy link

One nice possibility on the frontend might be making widgets as Web Components (perhaps with Polymer). That would allow them to be implemented/styled/etc in a way that is sandboxed from the rest of the page.

@jasongrout
Copy link
Member

IIRC, Escher, the IJulia widget system, uses webcomponents and polymer a lot: https://shashi.github.io/Escher.jl/ (see also https://groups.google.com/forum/#!topic/julia-users/UEaYPlBuIkc for a brief description of how it works)

@ellisonbg
Copy link
Member

I am going to looking into webcomponents - I think it could be useful for
us...

On Tue, Jun 16, 2015 at 12:15 PM, Jason Grout notifications@github.com
wrote:

IIRC, Escher, the IJulia widget system, uses webcomponents and polymer a
lot: https://shashi.github.io/Escher.jl/ (see also
https://groups.google.com/forum/#!topic/julia-users/UEaYPlBuIkc for a
brief description of how it works)


Reply to this email directly or view it on GitHub
#13 (comment).

Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger@calpoly.edu and ellisonbg@gmail.com

@minrk
Copy link
Contributor

minrk commented Jun 18, 2015

@willwhitney thanks! I think that's a good idea.

@jasongrout
Copy link
Member

I think web components is finally maturing enough to start looking at it. When I looked at it several years ago for the sage cell server, it wasn't mature enough/supported in browsers enough.

@jasongrout jasongrout reopened this Jun 18, 2015
@jdfreder jdfreder modified the milestones: 5.0, 4.1.0, 4.2 Oct 16, 2015
@jdfreder jdfreder mentioned this issue Oct 20, 2015
@jdfreder jdfreder modified the milestones: 4.2, 5.0 Oct 30, 2015
@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 21, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
proposal resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants