| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
| |
The user's premise: show what pwndbg shows, hide nothing; the semantic
views stay as a lens on the machine. So every frame holds the registers
(all, each followed as a pointer), the stack telescope and the backtrace
in a column that never changes, and the source, the disassembly and the
scene's lens in the other. A value's ink says where it points (stack,
heap, code, data; rwx underlined), its paper says what happened to it.
JetBrains Mono NL for everything mono; the floor is mono 20, which a
phone does not read: what narration depends on is also in the caption.
Mocks 9 to 11 are drawn from a real recording of targets/list.
|
| |
|
|
|
|
|
|
|
|
| |
motion.md: the animation principles as they apply here, a timing chart at
60 fps for each kind of event, revised motion tokens, and a timestamped
critique of the five scenes as first rendered. motion/motion.py draws a
per-panel timing chart of a video and tiles its frames into contact
sheets; charts/ and sheets/ are what the critique was read from. Measured:
in fib 75 steps start three or more panels on the same frame, 68 changes
have no frame in between, and the run is 68 evenly spaced steps.
|
|
|
Lapis page and vellum ink; a role is a form as well as a colour (current,
write, read, pointer, allocated, freed, fault, kernel); panels as acme
windows; Go Mono for the machine and Go for the narrator; motion as whole
frames at 60 fps. design/mock/gen.py redraws the mocks from the tokens.
|