-
Notifications
You must be signed in to change notification settings - Fork 950
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
Using ipywidgets with standalone cell view/output #3946
Comments
It is pretty easy to pretend that we have a console and use registerConsoleWidgetManager(
{console: {
sessionContext,
rendermime,
disposed: outputArea.disposed
}} as any,
chain(widgetOutputs())
) |
Agreed! I understand #3922 would go in that direction. Though it may be quite breaking (I only assume, haven't reviewed yet). I'm not sure I like the idea of breaking the APIs, ipywidgets 8 was already quite disruptive. |
I've been working on the PR jtpio/ipylab#135 for ipylab that uses #3922. For a per-kernel widget manager the following line enables Ipywidgets for a kernel.
It is foreseeable that widgets could be automatically enabled for any Python kernel started or registered in Jupyterlab. The screenshots below demonstrate the capabilities of ipylab combined with the per-kernel widget manager.
I've been using these new features for months in Jupyterlab 4 without major issue. I'm no expert in Jupyterlab or Ipywidgets and would appreciate guidance / collaboration from an expert. Create launchersControl of Jupyterlab and adding widgets to the main area |
Problem
It's currently hard to use ipywidgets outside of existing notebook and console widgets. It should not be.
Proposed Solution
Expose
registerWidgetHandler
? Generalize it to takeNotebook | Console | IDisposable
argument?ipywidgets/python/jupyterlab_widgets/src/plugin.ts
Lines 168 to 174 in b24fa6b
Additional context
Related to jupyterlab/jupyterlab#16227
The text was updated successfully, but these errors were encountered: