formal decoder spec #3
Description
Restructure processing into formal stages, populate a virtual model/index, and obtain a descriptor to scaffold the UI without rendering any data. Think of it as a preloading a lazy DOM over the trace. I think a reactive pattern/pipeline would work best overall (if good with perf).
First pass:
- discover segments / messages -- remember boundaries
- count events of each type -- segment stats
- pin initial topologies per segment so we can show the graph as soon as it's selected
- etc.
After the first pass, the user selects a segment.
Only when a segment is selected do we actually transform its trace into the viz model for time travelling.