[timingobject] Chaining timing objects

tidoust has just created a new issue for 
https://github.com/webtiming/timingobject:

== Chaining timing objects ==
Creating an issue to track this idea that Ingar raised on the 
mailing-list:
https://lists.w3.org/Archives/Public/public-webtiming/2015Jul/0006.html

Being able to create a hierarchy of `TimingObject` objects would make 
it possible to create timing objects that can *process and convert* 
the state vector of another timing object, e.g. to convert the 
position from one unit to another or to shift or skew the position so 
that it matches a media timeline.

The spec should define a few of these *processing* types of 
`TimingObject` objects for that to be useful.

I'm not sure how we can create a type of TimingObject that could be 
associated with custom JavaScript code that does the processing. 
Without having given it more thoughts, an approach similar to that 
used in the `createAudioWorker` method of the Web Audio API [1] where 
the code runs in a separate Worker could be useful. Incidently, that 
mechanism is quite similar to the idea of running the timing provider 
code in a separate JavaScript realm (see issue #10), so there might be
 a way to merge the two ideas into one.

[1] 
http://webaudio.github.io/web-audio-api/#widl-AudioContext-createAudioWorker-Promise-AudioWorker


See https://github.com/webtiming/timingobject/issues/13

Received on Thursday, 23 July 2015 13:01:24 UTC