so it should be straightforward... at least once the bone's forwards are calculated, which I believe is going to be "the angle the bone is when loaded" once we get to glTF armatures

and here's X

picking different forwards for bones is easy though. here's negative z

not currently "keeping" the original angles, instead choosing to use z-forward (probably should be neg-z forward though)

I've got positions and rotations, but not at the same time :laughing:

The info from the query includes language, etc so you can set it directly in whatever you use for screenshots.

I use transparent bg for the codeblocks, which makes it easier to place/rescale/etc into videos.

I'll can more of a writeup soon showing more details and some images and such.

The query is basically this. (nushell, so insert jq or whatever you like):

typst query main.typ "raw" | from json | where block | get text | save output.codeblocks.json

This dumps all codeblocks into a json file as an array of strings. Then I take this file and ingest it into remotion for stills.

yeah, I'm not particularly happy with the codeblock screenshots at the moment (its a bit slow, but not slower than doing it manually) so I haven't written it up but its basically regular codeblocks in typst (any raw codeblock will do, the query actually returns blocks and inline).

100 lines is not too bad but I do find myself pulling this lib.typ into multiple projects and it will definitely grow more (custom note needs a PDF target impl and such)

Nice, I'll have to check those packages out.

The single lib.typ is because most of it is "switch configuration based on target" for things like image handling. It's only 100 lines or so and provides about 3 functions (a template, code highlight, custom note)

github.com/ChristopherB...

root is in one of these piles... somewhere... I think...

Can you upload this to my nightly branch. Haven't seen much sleep lately.