You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get the JS kernel to support the Jupyter Widget message spec. Unfortunately, the most professionally-maintained JS kernel does't have a story yet so we'll be inventing new stuff.
desired API
How should widgets be available?
wydgets whole new API opinion
@jupyter-widgets/jupyterlab-manager somehow use the registry directly
letx=widgets.FloatSlider({description: 'x'});display.display(x);// a widget appears in the output areax.value=1.0// item moves along axisx.jsobserve('value',(change)=>{document.write(change.new)})// page streams changed valueswidgets.jsdlink([x,'value'],[x,'description'],(value)=>{`${value} %`}// some weird labelling stuff happens
approaches
use the widget registry directly to generate an API of the available widgets?
down the road
if a live jyve kernel (or proxy) has direct access to the WidgetManager, there's no reason it couldn't have access to all the widgets in all the notebooks, and be able to manage linkages between them.
The text was updated successfully, but these errors were encountered:
Get the JS kernel to support the Jupyter Widget message spec. Unfortunately, the most professionally-maintained JS kernel does't have a story yet so we'll be inventing new stuff.
desired API
How should widgets be available?
wydgets
whole new API opinion@jupyter-widgets/jupyterlab-manager
somehow use the registry directlyapproaches
down the road
WidgetManager
, there's no reason it couldn't have access to all the widgets in all the notebooks, and be able to manage linkages between them.The text was updated successfully, but these errors were encountered: