Re: AU parameter groups proposal
Re: AU parameter groups proposal
- Subject: Re: AU parameter groups proposal
- From: James Coker <email@hidden>
- Date: Tue, 10 Jun 2003 17:30:22 -0600
On Tuesday, June 10, 2003, at 02:06 PM, Marc Poirier wrote:
As has been mentioned before, some folks think that it would be great
if
AUs could define parameter groups for their parameters. I agree, and I
just thought of a possibly good way to implement it.
[big snip]
So that's my idea for how to add this feature. What do others think?
I like this idea, but don't know enough yet about AU parameters to
comment on the technical details. However, I would like to mention
that I think indexed parameters would also help immensely with large
plugins. This technique has been in the JavaBeans spec for years, and
is
a very nice way to handle parameters that naturally fit into arrays.
A description of JavaBeans indexed properties is at:
http://java.sun.com/docs/books/tutorial/javabeans/properties/
indexed.html
It also appears in the JavaBeans spec, and is also used in EJB.
It basically just adds an array index parameter to the get/set
calls used to access parameters.
For instance, if your plugin has 15 LFO's, instead of defining fifteen
frequency parameters, one for each LFO, you can define one parameter
with a maximum index of 15. I use this approach internally for
Numerology and it makes parameter management much easier.
This grouping is a bit different from the grouping Marc describes,
but does not have to conflict with that grouping. Marc's grouping
proposal is something that would primarily be used at the UI level to
improve the user experience, whereas indexed parameters are a grouping
used at the implementation level to improve the programming experience.
Cheers,
Jim
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.