Should user explicitly init the declarative widget system about declarativewidgets HOT 6 CLOSED

Would this remove the need to preload polymer and the urth channel stuff on every notebook page, even when widgets aren't used? Would that happen after widgets.init()?

from declarativewidgets.

@parente that is the point. Nothing gets preloaded until the cell with unit is ran. Maybe only the minimum js would be on all pages.

from declarativewidgets.

Maybe only the minimum js would be on all pages.

I was after even removing this. For instance, the %matplotlib notebook magic injects all the JS it needs only after this call. Nothing needs to be in Jupyter before then and so it doesn't need to be an extension to Jupyter. It would be very cool if the widgets could reach that point (but I know that would involve some kind of replacement for the urth_import server handler which probably is not replaceable.)

from declarativewidgets.

We would still need the extension to have the js available for download. But I agree that nothing needs to be preloaded on the browser, if possible.

from declarativewidgets.

Was doing some experimentation on this. I thought that I could block the kernel from returning from the cell run and orchestrate init though the COM channel. This is not possible because COM channel browser -> kernel is done through the shell channel also.

I also did not see a way to pausing running of cells from the browser side.

I'm going to leave this one open, but will move to work on something else.

from declarativewidgets.

Thought on how the kernel init code can interact with the browser to cause the init.

Using Comm.

1. Our extension will register a comm target with a name like jupyter_declarativewidgets_init and provide a handler (https://github.com/jupyter/notebook/blob/master/notebook/static/services/kernels/comm.js#L46)
2. The code on the kernel side (widgets.init()) will send a COMM_OPEN message to that target. That should trigger the browser code on https://github.com/jupyter/notebook/blob/master/notebook/static/services/kernels/comm.js#L78 that would then call our handler.
3. There might be an optional handshake to let the kernel side know that all is ready and that could take place through the same COMM channel.

CommManager will then become another dependency that would have to be injected into our env.

from declarativewidgets.