Cute example, but causing massive usability headaches - need to pull the methods that generate a URL (and the relevant data) for export into it's own set of functions that can be called in the background (or through UI/NSDocument) and NOT implicitly invoked on state updates from swiftUI. Doh!

The mechanism that I have in place works fine for small values, but it quadratic and goes to crap quiclyl with large bursts of data (1,000+ values), and ends up locking the CPU doing the gymnastics to count the values returned - which shouldn't be that bad, but I was foolish.

Redesign this whole flow so that the UI updates as we get receipts for sent values, but doesn't use quadratic computation insanity.

refactor the kit to try and use UIDocument, and see if that nets things further. It's exporting, but there's some hang where you never get an end-state when it's done exporting. I suspect the UIKit stuff "auto-dismisses" but that's not happening with SwiftUI

the holy grail of spans - show multiple spans as they overlap with bars or such, and annotated events so we can see what happened and when

Could be done with a Promise library, or with Combine - but it should also respect delay setting and run off a background queue

create a view that can provide visual output from a Span - an individual element, so they can be inspected with a text view

break up the component views and refactor them down to the basics so they're easier to mix and match, and remove what's no longer relevant

it'd be lovely to have a time based view of a single span that could be placed relative to other spans