- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Dec 2012 19:20:54 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20381 Bug ID: 20381 Summary: MIDIInput and MIDIOutput should inherit from MIDIPort, which should not be an interface Classification: Unclassified Product: AudioWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: MIDI API Assignee: dave.null@w3.org Reporter: cwilso@gmail.com QA Contact: public-audio@w3.org >From Marcos: It would be better if you could fold everything into MIDIPort and get rid of MIDIOutput and MIDIInput? you already have the port type, and you can just say that sending() does nothing when a port is not outputting. If you don't agree, then I think MIDIInput and MIDIOutput need to inherit from MIDIPort (not implement the interface). Implementing the interface makes a huge mess when actually implementing, as the stuff from MIDIPort has to be copied over from MIDIPort. So, worst case, please change the spec to match the following pattern: interface MIDIOutput : MIDIPort { } interface MIDIInput : MIDIPort { } MIDIPort : EventTarget{ } However, I strongly urge you to do away with MIDIInput and MIDIOutput. They are redundant, IMHO. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 13 December 2012 19:20:55 UTC