-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time scrubber for kepler component #262
Comments
Yes very into this idea. Current view state should be a pure function of time and properties - we should be able to compute the values at a given timestamp easily without needing to compute everything that came before it. Let's make this a higher priority. |
It's really easy to implement too since hubble already ships a "seek" function. This is just a UI change where the main thing to figure out is which design to go with. I had one drafted - I'll export some screens and states today for feedback. |
I think I'd prefer a more keyframe-centric design but this is great as a starting point! Really good place to jump off from. |
Have any examples? I think I agree, but keyframe-centric design can mean so many things. I have another design approach I'll share for a one-track keyframe editor, which could be used in applications that only need one track, like a "magic keyframe" timeline discussed in #43 I think the basic time scrubber can get built within a couple days because it's so simple, whereas designing keyframe-centric sounds like a bigger effort. |
See the prior art section of https://observablehq.com/@akre54/animator-lib-proposal I'm thinking more specifically like Theater.js: https://www.theatrejs.com/docs/latest/manual/sequences Don't disagree this is a necessary first step. |
Currently it's difficult and time consuming to preview the ending of an animation because it needs to played back in full.
A simple time scrubber in the kepler video export component would solve this issue, and allow users to see any moment in the animation before rendering.
The text was updated successfully, but these errors were encountered: