Re: Thoughts and questions on the API from a modular synth point of view

Ah, thanks. I will read through that list.

>  AudioParam.name was removed: https://www.w3.org/Bugs/**
Public/show_bug.cgi?id=17397<https://www.w3.org/Bugs/Public/show_bug.cgi?id=17397>


Why was it removed? I can't see any harm in it being there if someone
doesn't use it. My approach is that i'd like nodes to completely draw
themselves, retrieving all necessary data from the object (and its
parameters) itself. A lenghty full description might be too much, but a
parameter having a short name doesn't seem like a very strange property.
Someone replied earlier that these params are all described in the
specification and that i can look it up there, but that argument holds as
well for the min/max-values, yet they are supplied.



2012/7/18 Marcus Geelnard <mage@opera.com>

> Hi Peter!
>
> Some of your questions are being dealt with in the bug tracker. Chime in
> if you have more input.
>
>
> Den 2012-07-15 05:50:08 skrev Peter van der Noord <peterdunord@gmail.com>:
>
>
>  - is there a way to retrieve more info about an audioparam? (name,
>> description)
>>
>
> AudioParam.name was removed: https://www.w3.org/Bugs/**
> Public/show_bug.cgi?id=17397<https://www.w3.org/Bugs/Public/show_bug.cgi?id=17397>
>
>
>
>  - It looks like the JavaScriptAudioNode has an unchangable number of
>> inputs and output. This freaks me out :) Is it going to stay this way?
>>
>
> https://www.w3.org/Bugs/**Public/show_bug.cgi?id=17533<https://www.w3.org/Bugs/Public/show_bug.cgi?id=17533>
>
>
>
>  - Can't i add Audioparams on a javascript audio node?
>>
>
> https://www.w3.org/Bugs/**Public/show_bug.cgi?id=17388<https://www.w3.org/Bugs/Public/show_bug.cgi?id=17388>
>
>
>
> /Marcus
>
>
>
> --
> Marcus Geelnard
> Core Graphics Developer
> Opera Software ASA
>