Re: [css-houdini-drafts] [css-animationworklet] proposal for sequence AnimationTimeline (#949)

I understand the power that having multiple timeline can provide. While did initially tried to allow multiple timelines (as you have noticed in our older demos) but it was considered too complex and not a good match for integration with web-animations. So it was dropped.

The particular usecase that we intended multiple timelines for was to mix "time-based" and "scroll-based" timelines.

> I had an usecase where I grouped the Effects (since a sequence is allowed), but I wanted them to be on distinct ScrollTimelines (to use different ranges and offsets)

I wonder can you use a single ScrollTimeline with the largest range and manually calculate the current time of other timelines inside the your `animate()` function and use that for each sub-effect of the group effect.


> I believe allowing a sequence of multiple timelines (a 1:1 relation to the sequenced Effects, fallback to default timeline if sequence length is unequal) could be a great benefit if natively supported. This would allow for a basic free Choregraphy support (think of the timelines as a Ballet where dancers have their own rythm), until Yi proposals ship for more concrete types.

If you need 1:1 relation between timeline and effects then I think that can be declared using multiple animations. No? It is the cases where you don't want 1:1 relationship that cannot be modeled with multiple animations (e.g., a single effect which is driven from two timelines)

> Is it intended to be in a future part of the spec ?
We are pursuing a different approach for handling the usecase where you want to mix input/scroll + time in Animation Worklet. It is documented here: https://discourse.wicg.io/t/proposal-exposing-input-events-to-worker-threads/3479

So at the moment we don't have any plans to work on multiple timelines.










-- 
GitHub Notification of comment by majido
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/949#issuecomment-533363617 using your GitHub account

Received on Friday, 20 September 2019 01:09:28 UTC