W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 17407] (NamingInconsistency): Interface naming inconsistency

From: <bugzilla@jessica.w3.org>
Date: Fri, 05 Oct 2012 18:56:54 +0000
Message-Id: <E1TKD4w-0007X3-P6@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17407

Chris Rogers <crogers@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crogers@google.com

--- Comment #1 from Chris Rogers <crogers@google.com> 2012-10-05 18:56:54 UTC ---
Here is a suggested re-naming which is more consistent.  Using this naming,
"Audio" is still present in AudioBufferSourceNode because "AudioBuffer" is the
name of the object used by this node.  "Audio" is still present in
MediaElementAudioSourceNode and MediaStreamAudioSourceNode because it's
important to distinguish audio from video.

AudioBufferSourceNode
MediaElementAudioSourceNode
MediaStreamAudioSourceNode
JavaScriptAudioNode ------------> ScriptProcessorNode
RealtimeAnalyserNode ------------> AnalyserNode
AudioGainNode ------------> GainNode
DelayNode
BiquadFilterNode
AudioPannerNode ------------> PannerNode
ConvolverNode
AudioChannelSplitter ------------> ChannelSplitterNode
AudioChannelMerger ------------> ChannelMergerNode
DynamicsCompressorNode
Oscillator ------------> OscillatorNode

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 5 October 2012 18:56:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:14 UTC