With your recent computer issues @bradleyboehmke, I think we should tear off the bandaid and move on from Rise. That has two main benefits:
We'll both be using the same coding environment as the students, which should make things easier to follow.
We can get rid of the special code that hides input code in Rise slides, and replace it with something that works with the nbconvert --to slides command.
This PR implements the change explained in 2, above: it removes the slide_tools.py file and all imports of it in notebooks, along with invocations of hide_code_in_slideshow. I added a special tag to the slides whose input should be hidden, and through a flag to jupyter nbconvert, automatically hid those inputs in the revealjs slides.
I also sneaked in a relatively unrelated change: parallelizing the bash script that converts notebooks to slides. This comes with a pretty decent improvement in the speed of that conversion, which we have to run each time we want to see updated slides based on our notebooks.
With your recent computer issues @bradleyboehmke, I think we should tear off the bandaid and move on from Rise. That has two main benefits:
nbconvert --to slides
command.This PR implements the change explained in 2, above: it removes the
slide_tools.py
file and all imports of it in notebooks, along with invocations ofhide_code_in_slideshow
. I added a special tag to the slides whose input should be hidden, and through a flag tojupyter nbconvert
, automatically hid those inputs in the revealjs slides.I also sneaked in a relatively unrelated change: parallelizing the bash script that converts notebooks to slides. This comes with a pretty decent improvement in the speed of that conversion, which we have to run each time we want to see updated slides based on our notebooks.