Apparatus

I admire Apparatus which was brought to my attention by Bret Victor, whom I also admire. Been thinking about how I might connect apparatus to wiki. site

Our proof-of-concept is now an experimental plugin.

Reviewing commits from earlier this year, I noticed a thing about a "viewer". Not much in the way of docs, but looks like there are tests. We've created an initial plugin which includes the viewer (in a fashion similar to a video player). commit

Apparatus itself wants a whole browser for editing. Graphics editing inside a wiki page seems quite limiting -- not enough screen real estate. But while I was browsing the code and tests, I did find docs about self-hosting an installation. I containerized apparatus for use in a local installation: Container dobbs/apparatus

Many months ago I created a model in aprt.us to help explain why programming around time is so painful. Well, maybe I created that more so I could have a tool to think with next time I needed to reason about time-related code. Either way, I learned how to save and load my explorable. So... maybe create a transporter for moving a saved model into a wiki

There are many choices to make.

The apparatus editor offers ways to save a diagram to one's laptop and to reload it into an editor later.

Here we have hosted apparatus in a container under the same namespace but not really within wiki. apparatus.wiki.dbbs.co is a virtual host pointing to the containerized apparatus.

It begs questions about how to simplify a workflow for saving and publishing diagrams.

Since the apparatus data structure is json, can the json plugin be combined in some way?

I'm not crazy about that markup. I use the `X` an `Y` bounds to compute the height of the iframe. But I also wish the viewer could read the bounds from the diagram's .json.