- From: <bugzilla@jessica.w3.org>
- Date: Fri, 08 Jun 2012 09:43:28 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17408
Robert O'Callahan (Mozilla) <roc@ocallahan.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roc@ocallahan.org
--- Comment #3 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-06-08 09:43:28 UTC ---
(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.
--
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, 8 June 2012 09:43:31 UTC