Interactive figures in sphinx/readthedocs?

Hi,

I was wondering if it was possible to embed the interactive figures in the sphinx documentation pages.

All the ipywidgets are visible and interactive in the doc pages (https://ipywidgets.readthedocs.io/en/stable/examples/Widget List.html).

I tried building my documentation with ipympl instead of the inline backend, but only the control buttons are showing up, not the figure: instead of with the inline backend.

I’m thinking in principle, the figure is just using some javascript to display it in jupyter, so it should also be possible to show it in the doc pages. Many thanks for any help.

[nvaytet]

Hi Martin,

Thanks for the swift reply. I see, so everything is done on the kernel side. Now that i’m looking at it again more closely, I can indeed see that the kernel is working when i’m panning/zooming. And this is also the case for the classical notebook backend.

Ok, it’s not a huge deal, I thought it would have been nice to be able to use a single backend for everything. Right now, i’m having to juggle between 3 different backends: the nbAgg for the classical notebook, the ipympl for JupyterLab, and inline for the docs.

If you are interested (i know you guys at QuantStack like working with C++), we are working on a library for multi-dimensional arrays which is similar to xarray but with a C++ core under a python interface: https://scipp.github.io/index.html. So it’s also similar to xtensor but with the added labeled dimensions.

Cheers

[nvaytet]

Hey!

It looks interesting 😃 We also started to work on a similar package based on xtensor called xframe: https://github.com/xtensor-stack/xframe it is still at early development stage though.

Hi Martin, Yes we looked at xframe also (actually, it was probably xframe I wanted to reference in my post above, instead of xtensor), and we decided it was still a bit too early in development to rely on it for our science program. It would also have probably taken some time before we could incorporate changes such as event data (basically like a vector of arbitrary length vectors), physical units, and uncertainty propagation, all of which we needed from basically day 1. The lazy evaluation is, however, a really nice feature that we are still missing. We are keeping an eye on how things develop. Cheers.