For animation you could probably model it as an iterator that produces frames, where that iterator has a counter that increments with each frame, and use that counter as a measure of progress to figure out what should go in the frame. A frame would need a timestamp and maybe image data, or maybe just a data structure that describes what to draw.
Then to render, pull frames off the iterator, display each one, and wait enough time between them. Multiple tracks are like multiple iterators running in parallel, and then something to merge them. I'm using wgpu for the rendering, but sixtyfps might have its own thing?
Happy to chat more about this stuff! Email is in my profile.
For animation you could probably model it as an iterator that produces frames, where that iterator has a counter that increments with each frame, and use that counter as a measure of progress to figure out what should go in the frame. A frame would need a timestamp and maybe image data, or maybe just a data structure that describes what to draw.
Then to render, pull frames off the iterator, display each one, and wait enough time between them. Multiple tracks are like multiple iterators running in parallel, and then something to merge them. I'm using wgpu for the rendering, but sixtyfps might have its own thing?
Happy to chat more about this stuff! Email is in my profile.