You are correct; for the initial steps that involve creating the new DOM
node you will need to modify servo/servo. However, you will also need to
modify servo/media in order to process the missing message. You are
correct that using existing WebAudio node implementations as models for
this work is a good choice; oscillatornode.rs and OscillatorNode.webidl
is a relatively straightforward implementation that you could follow.
Cheers,
Josh
On 3/22/19 11:14 AM, Chris Benfante wrote:
Hi all!
My group is working on implementing ConstantSourceNode (#21803
<https://github.com/servo/servo/issues/21803>) and we have a few questions
on getting started.
It appears that our first step is creating the DOM Interface, but our
written instructions mention forking from the servo/media repository rather
than the main project because it takes a long time to build. However, we
don't see any files or code related to DOM interfaces for nodes, though I
did find them in the main project. The servo doc also seems to support
this:
https://doc.servo.org/script/dom/#adding-a-new-dom-interface
So, which fork should we create the DOM interface on? Also, which source
files should we reference most for this interface? The *node.rs files seem
like the best bet, but each have considerable variation in implementation.
Thanks!
Chris B.
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
