State Transition
Real data changes all the time. Redrawing the whole map on every change would be jarring, and you would lose track of what moved.
The map works out what changed and animates only that, in four steps: leavers fade out, tiles reshape, movers glide, newcomers appear. It holds up from 7 to 300 things.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
When data changes, only the things that changed move, so you can follow them.
Only what changed moves · came from Mark Parson
- Leavers fade, tiles reshape, movers glide, then newcomers appear. New in this cycle
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
qmap-c12-D1 Update only what changed rather than clearing and redrawing the scene. — Mark Parson
qmap-c12-D2 Keep the layout engine pure; working out the difference is a separate layer. — Mark Parson
When data changes, only the things that changed move, so you can follow them.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built the change-only animation system
The record names no one. The experiment code and this record reached the qmap repo in commits authored by Mark Parson.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 9
The full record 4 decisions · 4 key-change entries · 245 words · 9 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c12 →