Re: AU interface consistency
Re: AU interface consistency
- Subject: Re: AU interface consistency
- From: Bill Stewart <email@hidden>
- Date: Tue, 01 Oct 2002 12:52:15 -0700
on 1/10/02 10:32 AM, Chris Reed wrote:
>
I'd also like to point out that since the AU edit views are HIView
>
objects, they can be embedded in a window you own instead of having to
>
be in their own window. Unless I am mistaken, VST custom edit views are
>
always shown in their own window (perhaps that's the only way I've ever
>
seen it--I am not all that familiar with the VST API). I think this is
>
an important distinction, because it gives the host app a little more
>
control over edit view, even if it looks radically different than the
>
rest of the app's UI.
Yes indeed - that was one of the reasons we defined the API for the view
component as we did (and why AudioUnitHosting was written the way it was) -
to reinforce the fact that you don't "have" to have a separate window for
every units UI...
A small step...
Bill
>
-chris
>
>
>
On Monday, September 30, 2002, at 05:46 pm, email@hidden
>
wrote:
>
>
> Hi Art,
>
>
>
> What you say makes sense. I think maybe you misunderstand a bit where
>
> I'm coming from. Inconsistent interfaces don't reflect on just the AU
>
> developer, but have a negative effect on the usability of the
>
> application using it, and the entire system altogether.
>
>
>
> Maybe there is not an all encompassing solution, but something could
>
> be developed for damage control to help the situation. And maybe
>
> things won't be as bad as I envision, but when it comes to interface
>
> issues when left to individual opinion things usually become messy.
>
>
>
> -- John
>
>
>
>> I do not.
>
>>
>
>> Custom UIs aren't simply a question of looking better, they allow
>
>> developers to add functionality that isn't possible with the standard
>
>> notion of 'parameter'. If you ignore my custom User Interface and my
>
>> plug-in needs the ability to load samples, what is the user to do?
>
>> Or what if my plug-in supports dynamic parameters of some sort, like
>
>> an envelope with an arbitrary number of breakpoints? Or a
>
>> waveshaping plug where the user can draw the shape? IMNSHO, these
>
>> issues can never be addressed by common controls, because (hopefully)
>
>> as soon as we standardize an arbitrary-point envelope control,
>
>> someone will have the creative vision to come up with something new
>
>> you can do with these toys... that requires a new way of controlling
>
>> and visually representing it.
>
>>
>
>> Best,
>
>>
>
>> Art
>
>>>> 0xBA
>
> _______________________________________________
>
> 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.
>
_______________________________________________
>
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.
--
mailto:email@hidden
tel: +1 408 974 4056
__________________________________________________________________________
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
__________________________________________________________________________
_______________________________________________
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.