Re: Introduction

> So that brings me to one item of discussion, and I'd appreciate the team's
>> input on this.  Although I am new to the sources, I do not personally see
>> any reason why the WebAudio architecture must by definition be tied to web
>> browsers.  Of course I see that the WebAudio objects are all accessible and
>> manipulable via JavaScript DOM, and I also see that the webkit/blink
>> implementation depends for some reason on the <wtf> headers, but I do not
>> see any technical reason why this implementation might be forked and
>> repurposed for native audio rendering applications.  If anyone can think of
>> a reason why this can't or shouldn't be done, I would love to hear it.
>>
>
> Hi John, good to hear from you.  Indeed, there is no technical reason why
> it can't be forked and re-purposed.  In fact, I'm pretty sure that this has
> already happened in at least one case.
>
>

Really?  Can you please tell me who did that, or whether the sources for
that port were ever made public?

My current thinking is that it might be a good start to fork the Blink
repository via a git subtree, get it running in conjunction with Phil
Burk's PortAudio low-level libraries, and then make the results available
via git somewhere.  Other opinions, crogers or anyone else?

---

John Byrd
Gigantic Software
2102 Business Center Drive
Suite 210-D
Irvine, CA   92612-1001
http://www.giganticsoftware.com
T: (949) 892-3526 F: (206) 309-0850