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

Re: [Bug 17793] New: AudioNode.disconnect() needs to be able to disconnect only one connection

From: Chris Wilson <cwilso@google.com>
Date: Fri, 20 Jul 2012 16:52:40 -0700
Message-ID: <CAJK2wqViug0KUwvLzh_BeczyunFN1QwZCQ2gOc_DuQ8MT0KSqA@mail.gmail.com>
To: Peter van der Noord <peterdunord@gmail.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
On Fri, Jul 20, 2012 at 4:18 PM, Peter van der Noord
<peterdunord@gmail.com>wrote:

> Hmm, whether you get the right input/output by providing an id-string or
> an index is not the issue, i prefer the id as well. I just think there is a
> lack of some core graph-interaction.
>

Probably true - I think the "derived class nodes" issue and JSNode dynamic
number of inputs/outputs should be discussed when Chris is back from
vacation.

In my opinion it is strange that disconnecting functionality is delivered
> only one-way (through outputs). As if i want to remove an element from the
> DOM, and the only way to do that is to look in every other element to see
> whether it contains the element i want to remove, and then remove it from
> the parent.
>

But that's kinda how it works.  If you want to remove a DOM node, you go to
its parent and call removeChild( node ) on the parent.  :)


> Don't get me wrong, i'm not suggesting removing those methods, i am aware
> that they are fully necessary for other types of applications than mine. I
> was hoping for an addition that could offer those functionalities by other
> means as well.
>

I think they're mostly there, except for needing to build a "composite"
node.

-C
Received on Friday, 20 July 2012 23:53:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 20 July 2012 23:53:09 GMT