Thank you for sharing all of this information. I sometimes also make a short video of the interactive code and post it as a companion demo. nb file and recommend the students should download it to run it themselves. The JupyterLab project seems to be going astray of that goal in my humble opinion.įWIW, my brute force default approach going forward is to just post the raw. This is definitely not warm and fuzzy when it comes to making the entire process clear for the non-tech-inclined. Certainly, the "roll your own meta-content lock codes for cells" approach to JupyterLab distributions belies an attitude that "we are coders, and you should be too". The inability to lock a file fully may be a current failing of JupyterLab and not IlumiDesk. ![]() So, I am still trying to find a way to distribute (interactive) notebooks in a locked-down environment in Canvas where they can be run but not altered or deleted. * (I can lock cells from editing and deleting by editing the cell meta-data - but any tech-inclined student can modify this in the IllumiDesk UI and destroy the file for everyone else down the line) * I cannot (easily if at all) lock the notebooks to prevent them from being deleted by any random student in the course. ![]() * I can now distribute those notebooks to all students in the course. * I can now generate JupyterLab notebooks in a workspace using IllumiDesk.
0 Comments
Leave a Reply. |