summaryrefslogtreecommitdiff
path: root/design
Commit message (Collapse)AuthorAge
* design: the band is two panels; what the first videos taughtGabriel Schneider12 days
| | | | | | | | | | | | | | | An independent review of the first videos, frame by frame, is placed in the catalogue. A lens is a drawing over the program column and its view over the state column (the dump; the backtrace for calls), which leaves the stack six slots as subject: the frame whole, from rsp to past rbp. Operands are whole. A mark covers the bytes that changed. A pin travels and keeps its side. A call's node is a projection of its return address. Fast passes are veiled. Captions have numbers a scene can be checked by, and a scene's first step comes by four seconds. Effects before causes and panels from different moments are forbidden by name. Mock 12 draws fib(4) calling fib(2) from the recording. Co-Authored-By: Claude Fable 5.2 <[email protected]>
* design: a language of named blocks; the lens as a band over the whole contextGabriel Schneider12 days
| | | | | | | | | | | | | The README is now the catalogue: atoms, rows, panels, ties, the frame and the verbs, each block specified once under the name the code uses, with rules of composition and what is forbidden. From the user's notes on the context mocks: a lens is a band across the top, its drawing on the left and the bytes it is drawn from on the right, a hexdump with each field's bytes marked and read at the row's end; the disassembly is seventeen rows in address order with a source-line column and an annotation for what each row read, set or jumped to; a register is pinned to the node it points at by name; hex is unbroken; and four kinds of tie say which pane is a view of which (thread, link, projection, echo).
* design, revision 2: the whole context in every frame, a lens beside itGabriel Schneider12 days
| | | | | | | | | | | | 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.
* design: the motion direction, with the instruments that measure itGabriel Schneider12 days
| | | | | | | | | | 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.
* design: the visual system canim follows, with eight mock framesGabriel Schneider12 days
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.