Jupyter notebook environment with the hide_code extension active upon session launch. No installation needed.
hide_code is a Jupyter notebook extension to selectively hide code, prompts and outputs with PDF and HTML exporting support.
Click a launch binder badge anywhere on this page to begin.
Note: Export to PDF via Latex button on the far right side of the hide_code toolbar doesn't work here. (ohhh, realized via a recent pull request here that links to issue#65 that the button for that has been bugged for a while now.) All other features, such as Export to PDF via HTML, are working.
This was a rather tricky extension to get working in sessions served from MyBinder.org/Binder. Solution based mainly on here and here. Getting export to PDF working from the hide_code toolbar required enabling wkhtmltopdf to work headlessly similar to had been done for Plotly Orca as I described here. serverproxy wasn't necessary for noteboook with hidden code to HTML when using the hide code menu on the toolbar pr for expoer to PDF from same toolbar.
Export to PDF via Latex button on the far right side of the hide_code toolbar doesn't work. I didn't try looking into what is necessary for that. The Export to PDF via HTML button does work. UPDATE: Realized via a recent pull request here that links to issue#65 that the button for that has been bugged for a while now.
still to do:
- make better demo notebook since that was just a placeholder and while widgets do seem to render it would be nice to have a non-widgest plot there too. Do dataframes work? (if so, would be nice to point out over on dataframe2image as easier route/related route if just need to make a document with a dataframe showing). Was there a good one at the hide_code repo? ==> YES. See demo.ipynb) in the development branch (dev branch) is the one used to make the animation amd should step through that to illustrate use. Copied that one used to make the animation into rep for now as
demo.ipynb. - for original repo and port all this over there and make a pull request noting that the badge URL would need fixing after the pull.