Viz Libraries
Our two visualisation libraries, a 3D network map and a 2D traffic flow, were nearly ready but undocumented and hard to use outside their own projects.
Both got proper package names and live demos on the design site: an overview of when to use which, and a page for each.
Documents
With file names, on their own page →Threads
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
The design site has a Visualization section: an overview of when to use which, and a live page for each library.
Live demos and a guide to choosing · came from Mark Parsonopen →
- Both libraries moved under the company's package label, ready to publish later. In words
- The site points straight at each library's source, so changes show up live, and the heavy 3D and 2D engines load only in the browser. In words
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.
c24-D1 The viz libraries stay standalone packages, not layers; the design site points at their source for live reload. — Mark Parson
The design site has a Visualization section: an overview of when to use which, and a live page for each library.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked to bring qmap and qflow into the site
Asked to check both projects, find what they needed to be usable, and document them on the design site.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 0 decisions · 11 key-change entries · 477 words · 1 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 c24 →