Re: Hardware control surfaces (was Re: Private Parameters)
Re: Hardware control surfaces (was Re: Private Parameters)
- Subject: Re: Hardware control surfaces (was Re: Private Parameters)
- From: Urs Heckmann <email@hidden>
- Date: Sat, 19 Jul 2003 10:14:41 +0200
Am Samstag, 19.07.03, um 02:08 Uhr (Europe/Berlin) schrieb Chris Reed:
On Friday, Jul 18, 2003, at 18:53 US/Central, Bill Stewart wrote:
Gang (then they can all have different colours and fight amongst
themselves :)
I think we're narrowing this down to Category or Collection...
I second Brian's suggestion of "page".
I throw in "slot" so we can call any managing object the slot machine...
Seriously, I think "collection" would be as misunderstandable as
"enumeration". Many names for grouping match common terms in
programming languages/concepts. Such terms should better be avoided...
Also, I think "Category" is supa-misleading. If it is sematically 100%
equal to the German "Kategorie", then it's just the opposite of what we
want. Any group of parameters that belong together is presumably tied
to a plugin's internal entity or module. If there are several such
modules that are conceptually similar, each matching parameter would be
of the same category, like if you have 2 filters, both cutoff
parameters would be the same category accross module bounds. If we had
a mixer, we'd group parameters of a channel strip. Each channel strip
has parameters of the categories Gain/Volume, EQ, Sends, etc...
Page. Hmm. To me, it sounds to much like made for the described usage
in hardware controls. But those groups have many more uses. Like
selective preset retrieval, layout improvements in generic views...
Hm. I better leave it up to the native English speakers...
Cheers,
;) Urs
_______________________________________________
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.