Skip to page content

[2020-09-09 Wed 09:04]

Yesterday I did some work in the garden and with qtMUD: my focus in the garden was processing compost, and in qtMUD, I was drafting up documentation, taking steps to get the code into a state that I can release.

As Christopher Webber makes progress with his Spritely project, I continue to get questions if qtMUD is related to it or relies on it: after all, Spritely is for “distributed programming” and uses “distributed virtual worlds” as one of the examples of what that could be, and qtMUD is code for running a virtual reality.

At this point, the answer is “no, no relationship.” Spritely is, frankly, way above my understanding of computers and programming at this point. I’ve had concepts like OCAP patiently explained to me, repeatedly, and I just… don’t quite get it.

Which is a little embarassing, but also, fine: qtMUD has so far been a project where everything I know how to do with it, I learned how to do through hacking with the basics myself.

In less embarassing news, I finally figured out how to install my qtMUD code as a local racket package, which also builds its documentation. So I’ve finally begun drafting documentation for qtMUD’s API - and not a moment too soon, as there’s something like 40 procedures in the engine and more in the library. It’s a lot to keep track of all in my head!* Footnotes