W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: [web-audio-api] (NamingInconsistency): Interface naming inconsistency (#219)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:30:27 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/219/24244860@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17407#0) by Chris Rogers on W3C Bugzilla. Fri, 05 Oct 2012 18:56:54 GMT

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

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/219#issuecomment-24244860
Received on Wednesday, 11 September 2013 14:33:59 UTC

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