17408 2012-06-05 12:37:46 +0000 (NodeCreation): Node creation syntax 2012-09-10 10:11:22 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED INVALID P2 normal TBD 1 mike dave.null mage olivier.thereaux philipj public-audio roc dave.null oldest_to_newest 68720 0 mike 2012-06-05 12:37:46 +0000 Audio-ISSUE-26 (NodeCreation): Node creation syntax http://www.w3.org/2011/audio/track/issues/26 Raised by: Marcus Geelnard On product: Each node has its own create* method on the AudioContext object. A common way is to use a single method taking a string argument giving the object name and an optional parameter object for object-specific parameters. Examples: document.createElement() and canvas.getContext(). While semantically similar, using a single create* method is probably preferable over many different create* methods (e.g less namespace pollution, clearer extensibility mechanism and more consistent with other Web interfaces). 68821 1 olivier.thereaux 2012-06-07 15:11:46 +0000 Comment from Robert O'Callahan, 15 May 2012, « I actually think the current set of methods is better. They're in the AudioContext so namespace pollution isn't a problem. Adding new methods is a perfectly adequate extension point. canvas.getContext() is a mess and being consistent with it is not a virtue. » 68870 2 philipj 2012-06-08 09:25:24 +0000 It seems like this provoked roc to blog: http://robert.ocallahan.org/2012/05/canvas-getcontext-mistake.html However, MediaStream Processing's createProcessor looks like it's repeating the "getContext() mistake": https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html#mediastream-extensions That being said, I'm having a hard time forming a strong opinion on this issue. 68872 3 roc 2012-06-08 09:43:28 +0000 (In reply to comment #2) > It seems like this provoked roc to blog: > > http://robert.ocallahan.org/2012/05/canvas-getcontext-mistake.html That is germane, but it isn't what provoked me to blog... > However, MediaStream Processing's createProcessor looks like it's repeating the > "getContext() mistake": > > https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html#mediastream-extensions Oops. Hoist by my own petard! > That being said, I'm having a hard time forming a strong opinion on this issue. I stand by my blog post. (In reply to comment #0) > A common way is to use a single method taking a string argument giving the > object name and an optional parameter object for object-specific parameters. > > Examples: document.createElement() and canvas.getContext(). > > While semantically similar, using a single create* method is probably > preferable over many different create* methods (e.g less namespace pollution, > clearer extensibility mechanism and more consistent with other Web interfaces). document.createElement() is different because there's an infinite number of different HTML elements you can create, so a finite number of create methods can't work. Also, "document" and especially "window" are such large and generic interfaces that adding dozens of new methods to them is undesirable. Canvas elements and AudioContexts don't have that problem. 68944 4 mage 2012-06-12 06:36:38 +0000 Points taken. I especially agree that as an extension mechanism, checking the presence of an object property is better than having to create an object an check if it succeeded or not. 73526 5 olivier.thereaux 2012-09-10 10:11:22 +0000 No objection since June, closing.