Steve

Thanks. If you like, I'll leave this open for now and update when I settle on a solution for preparing statistical analysis docs. I like the TeX/LaTeX approach in metys,...

> If you are using JupyterLab there is also an extension for Vega-Lite that allows one to pass the JSON based Vega-Lite description right to the front end. Eventually I...

Is the extension still required? I was able to generate some Vega-Lite graphs with JupyterLab 3.0.9 by creating a spec file and double clicking on it. See https://jupyterlab.readthedocs.io/en/stable/user/file_formats.html#vega-vega-lite. I admit...

Interesting. I never heard of shasht before. I'll have a look. I might just try to work around any issues in yason with a macro, or maybe work with the...

Can shasht handle encoding of nested alists? For example in the above (though not an alist, imagine it is): ``` ("encoding" (jsown:new-js ("x" (jsown:new-js ("field" "a") ("type" "ordinal"))) ("y" (jsown:new-js...

> If you are using JupyterLab there is also an extension for Vega-Lite that allows one to pass the JSON based Vega-Lite description right to the front end. Eventually I...

I was thinking of a way to save a JSON spec in a variable, or as part of a plot class. The jsown is a bit wordy to work with...

I see. In fact if you look at the new-js output: ``` (:OBJ ("$schema" . "https://vega.github.io/schema/vega-lite/v3.json") ("description" . "A simple bar chart with embedded data.") ("data" :OBJ ("values" (:OBJ ("a"...

It looks like this is related to issue #80 that I just opened. #72 has been merged; does it allow for sending proper alists?

The plot specifications for Vega-Lite are all manipulated as alists. How can we get shasht to encode them? The example above: ``` (jupyter:inline-result '(:object-alist ("$schema" . "https://vega.github.io/schema/vega-lite/v4.json") ("description" . "A...