Add a serializer to MIDIPort

[jussi-kalliokoski]

Originally reported on W3C Bugzilla ISSUE-20415 Mon, 17 Dec 2012 17:21:11 GMT Reported by Jussi Kalliokoski Assigned to This bug has no owner yet - up for the taking

See this thread: http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0697.html

[jussi-kalliokoski]

Original comment by Chris Wilson on W3C Bugzilla. Mon, 17 Dec 2012 18:51:13 GMT

Can you describe exactly what feature you're trying to get from this (i.e. user scenario)?

[jussi-kalliokoski]

Original comment by Marcos Caceres on W3C Bugzilla. Mon, 17 Dec 2012 20:57:09 GMT

(In reply to comment #1)

Can you describe exactly what feature you're trying to get from this (i.e. user scenario)?

See "9.2 Enumerating Inputs and Outputs" example: https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html#enumerating-inputs-and-outputs

That's pretty common... with toJSON, it becomes something like:

function showPorts( midiAccess ) { function show(port, i){ console.log("Input port #" + i + " " + port.toJSON()); } midiAccess.enumerateInputs().forEach(show); midiAccess.enumerateOutputs().forEach(show); }

[jussi-kalliokoski]

Original comment by Chris Wilson on W3C Bugzilla. Mon, 17 Dec 2012 21:01:25 GMT

(In reply to comment #2)

(In reply to comment #1)

Can you describe exactly what feature you're trying to get from this (i.e. user scenario)?

See "9.2 Enumerating Inputs and Outputs" example: https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification. html#enumerating-inputs-and-outputs

That's pretty common... with toJSON, it becomes something like:

function showPorts( midiAccess ) { function show(port, i){ console.log("Input port #" + i + " " + port.toJSON()); } midiAccess.enumerateInputs().forEach(show); midiAccess.enumerateOutputs().forEach(show); }

That sample was just enumerating the parameters for debugging purposes, though - serialization implies deserialization. I don't think the "serialize everything in the input/output object" is a particularly interesting scenario, unless you're trying to imply that fromJSON() could re-create the port - and this is a "magic host object". :)

[jussi-kalliokoski]

Original comment by Marcos Caceres on W3C Bugzilla. Mon, 17 Dec 2012 23:16:20 GMT

(In reply to comment #3)

That sample was just enumerating the parameters for debugging purposes, though - serialization implies deserialization. I don't think the "serialize everything in the input/output object" is a particularly interesting scenario, unless you're trying to imply that fromJSON() could re-create the port - and this is a "magic host object". :)

Ok, fair call. I currently don't have a case for serialization (apart form using it as a stringifier in debugging).

I think there might be a case for storing serialized versions of previously used ports, etc. But I need to encounter the actual use case through playing around a bit more with the API....

Can we mark this as RESOLVED/NEEDSINFO?