Re: Web MIDI polyfill

Hehey, Chris!

Nice work! I'll try to make a demo for it as soon as I have some time!

A word (or two) about forward-polyfills though: You should have a prefix
for it (navigator.jazzGetMIDIAccess?) and not care whether there's a native
implementation around, that way it's not future-hostile. If future breaking
changes are made to the API and implementations are made accordingly, the
sites using the polyfill will possibly break in the user agents that are
implementing the spec correctly. While it's unlikely that we'll introduce
any breaking changes, it's possible as we're not even at LC yet, and it's a
good practice with forward-polyfills to keep up anyway. :)

Cheers,
Jussi

On Tue, Dec 11, 2012 at 3:13 AM, Chris Wilson <cwilso@google.com> wrote:

> I just wanted to let the group know that I've now also updated my Web MIDI
> API polyfill (https://github.com/cwilso/WebMIDIAPIShim), which builds on
> top of the Jazz-soft.net NPAPI plugin to add Web MIDI API support on OSX
> and Windows (if you install the Jazz plugin v1.2 or later).
>
> The polyfill uses the current syntax of the API in the specification; I
> also added multiple simultaneous I/O support (the polyfill could previously
> only support one input and one output at a time), sending and receiving
> long messages (system exclusive), support for timestamps (on send and
> receive), albeit of course with only setTimeout-level precision (it is a
> JavaScript polyfill, after all), and (I think) proper event dispatching
> (i.e. you can use addEventListener as well as onmessage).
>
> In short - you should be able to include this polyfill in a project, and
> it will add Web MIDI support to your browser.  (Caveat: have not thoroughly
> tested the cross-browser implementation; I know CustomEvent is not there on
> IE<10, which would be an issue.)
>
> Happy to take further suggestions.
>
> -Chris
>