I ran JOD Best Practices Lab.ipynb. On the whole, it ran well.
I found two places in the lab where I had to go to JQT to run setup options. I
had to use JQT to setup the JOD User Defined folders. I also had to use JQT to
set the PDFReader in base.cfg.
In both cases, I had to restart the lab to recognize the changes made in JQT.
I also found that, in many cases, the input blocks had to be executed in
sequence.
In general, I found the JOD Jupyter labs interesting and the display format very
nice.
Thanks,
David Mitchell
On 1/27/2019 15:12, John Baker wrote:
When I first encountered Jupyter Notebooks I thought they would make an
excellent delievery mechanism for J labs.
This weekend I converted some J/JOD labs to Jupyter.
Jupyter labs support a richer documentation and execution environment than
we are used to seeing with J labs. You get all the typographic goodies of
Markdown, code pretty printing and, best of all, the final result can be
easily browsed by anyone. Casual browsers do not have to install J to view
lab output.
I would recommend all addon and lab authors to consider producing Jupyter
versions. It will help expose J's delights to wider audiences.
Have a look:
https://github.com/bakerjd99/jod/blob/master/jodnotebooks/JOD%20Labs%20in%20Jupyter.ipynb
https://github.com/bakerjd99/jod/blob/master/jodnotebooks/JOD%20Introduction%20Lab.ipynb
https://github.com/bakerjd99/jod/blob/master/jodnotebooks/JOD%20Source%20Code%20Dump%20Scripts%20Lab.ipynb
https://github.com/bakerjd99/jod/blob/master/jodnotebooks/JOD%20Source%20Code%20Dump%20Scripts%20Lab.ipynb
John Baker
J'ugglar at Large
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
