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

Re: [web-audio-api] Node creation method naming inconsistencies (#166)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:30:03 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/166/24244625@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=18332#3) by Marcus Geelnard (Opera) on W3C Bugzilla. Wed, 17 Oct 2012 07:13:38 GMT

(In reply to [comment #3](#issuecomment-24244620))
> Now that 17407 is resolved, how do the two method name-changes sound?

Given your suggestion, we'd get:

createBufferSource -> AudioBufferSourceNode
createMediaElementSource -> MediaElementAudioSourceNode
createMediaStreamSource -> MediaStreamAudioSourceNode
createScriptProcessor -> ScriptProcessorNode
createAnalyser -> AnalyserNode
createGain -> GainNode
createDelay -> DelayNode
createBiquadFilter -> BiquadFilterNode
createWaveShaper -> WaveShaperNode
createPanner -> PannerNode
createConvolver -> ConvolverNode
createChannelSplitter -> ChannelSplitterNode
createChannelMerger -> ChannelMergerNode
createDynamicsCompressor -> DynamicsCompressorNode
createOscillator -> OscillatorNode

This looks very intuitive to me. The only thing sticking out here are the three first nodes, where "Audio" is somehow in the node name (which seems right IMO), but not in the create* method name.

I don't have any objections to that (shorter names = good thing™), other than the possible loss of distinction between Audio/Video Media sources that you mentioned in Bug 17407. Any thoughts?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:34:09 UTC

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