Open fsimkovic opened 6 years ago
Thanks for the report!
I don't know yet what causes the problem, but I've seen that there are similar problems when viewing on Github (https://github.com/fsimkovic/mmtf-pyspark/blob/master/demos/applications/MetalInteractionsAdvanced.ipynb), on nbviewer (http://nbviewer.jupyter.org/github/fsimkovic/mmtf-pyspark/blob/master/demos/applications/MetalInteractionsAdvanced.ipynb) and when converting the notebook to HTML with nbconvert
. It doesn't seem to work in JupyterLab, either.
I don't know if I have time to further look into that, you might want to report this to nbconvert
and JupyterLab, too.
If you find any clues, please keep this issue updated!
What data type is saved as result in the ipynb file? It looks like the result is a function that could not resolved by nbsphinx.
Using the
py3Dmol
extension in a notebook works fine but when converting the notebook withnbsphinx
the panel gets condensed to a narrow width.An example can be found on this page
https://mmtf-pyspark-test.readthedocs.io/en/latest/demos/applications/MetalInteractionsAdvanced.html#Visualize-Data
Disabling
overflow: auto
shows the panel in full width but obviously is not the solution to this problem. Wrapping the visualisation into anotherdiv
also works but the nextnboutput
remains on the same line.What's the best way to bypass this and get a full 700px by 700px viewer with the
Out
message on the next line?