Re: AU versions
Re: AU versions
- Subject: Re: AU versions
- From: Marc Poirier <email@hidden>
- Date: Thu, 31 Jul 2003 18:08:26 -0500 (CDT)
On Wed, 30 Jul 2003, Bill Stewart wrote:
>
Yes, you can read the version out of the resource, but I think there is
>
a simpler and more elegant way to do this... (and I'll make sure this
>
is in the SDK)...
That may be more elegant, but I don't think that it's simpler. Think
about it this way: the difference is between doing a little bit more work
for every single AU that you write vs. doing a little more work than that
but only once, in ComponentBase::Version. One of the things that I like
most about the AU SDK is how you only have to override 3 or 4 methods to
make a basic AU, and they are important ones. But little things like
Version being required in every AU start to clutter that up...
Also, having ComponentBase::Version do it via resource doesn't preclude
anyone from doing still overriding it if they want, for the
higher-version-for-debug trick that you mention.
But the main reason why I don't think that that solution is good enough is
because I think that, unless you make sure and knock every AU developer on
the head, they won't go back and do what they should have done from the
beginning (override Version), and we'll still have a situation where
virtually every AU does this incorrectly. Maybe I'm just pessimistic
about that, though. But at least an update to ComponentBase that gets
version from resource will mean that those AUs that are built or rebuilt
with the latest SDK sources will behave correctly.
But anyway, though I disagree with you somewhat, ComponentBase::Version
isn't really my main concern. My main concern is that the Component API
(I know, not your responsibility) doesn't have a convenient way to query
the version from resource. I guess that's because version was added to
the 'thng' v2 extended component resource type. It seems that there
hasn't been anything added to the Component API for conveniently fetching
that 'thng' v2 extra info like there is for getting the original 'thng'
infos, which is crummy. Really, I wish that the version selector was
obsoleted and that GetComponentVersion fetched it from resource instead.
That, and I want to make sure that host apps know use query AU version
from resource so that it's more efficient, if they're scanning AUs at
launch time. Those are my 2 big concerns.
>
BTW - this is taken from the offline AU that we've defined with the
>
help of Waves, and this reverse unit will be in the SDK in Panther...
That's fantastic news! :)
Thanks mate,
Marc
_______________________________________________
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.