Mostly for Sean, but perhaps of interest to others, maybe KDC. I've had my
assistant overhaul the conversion to Jupyter. @Sean - maybe pack the kids off
to overnight camp and explore? Definitely experimental, but also definitely a
huge leap forward, ansd maintainable, I think.
Need to use the pretext/pretext script, and your Python environment needs the
"nbformat" package. "-c jupyter", also an option for making a zip file of teh
collection. Please report any procedural issues.
https://github.com/PreTeXtBook/pretext/pull/3034
Principally we are trying to solve the "#sage in the middle of a block" problem
in a general way. It is stressing my assistant.
#interactive are in their static forms. This includes #video and #audio, but
maybe we can get that sorted soon. #sage become code cells using the "sagemath"
kernel. The publisher file will let you specify a "python3" kernel. Have not
thought too carefully beyond the Sage case.
Jupyter notebooks are very paranoid. We have placed CSS in an initial hidden
cell. You must execute it, or trust the notebook, or open it for a second time,
etc. We have no access to the MathJax configuration. I doubt #interactive will
run, though maybe if we just point to a server instance, those kinds will
behave? Or pointing to our standalone pages is enough?
I think a lot of necessary CSS is missing. I took some time to identify
#sidebyside and #tabular, plus a few other bits, as needing some additional CSS
rules to be functional. Likely more, on discovery and suggestion.
I had my assistant also provide a build for the Jupyter Book machinery. But now
I fail to see the point. Jupyter Book builds a pile of notebooks into a book
(duh) which is a static HTML site where the Sage code is also static (easily
copyable, but not executable). In other words, back to a (much inferior)
version of our base HTML conversion. With lots of compromises along the way.
And a "version 2 Myst rewrite" sounds hostile to our markdown-cells-as-HTML
approach. I have everything on this front saved, which I could bring back if
somebody can convince me why that would be a good idea.
@Sean - can you review and look for big glaring inconsistencies that we need to
fix so we can stop calling this experimental? I'm not ready yet for
APEX-specific things like asides. ;-) Clear and concise descriptions will
allow me to feed them to my assistant. Stuffing a YouTube video into a notebook
might be an interesting experiment that would benefit APEX (and everybody else).
Rob
PS Just learned that my assistant will continue to work for the same low wages
for another week before asking for a raise. Back to a serious upgrade of the
braille conversion, in-progress. ;-)