Re: Cocoa and AudioUnits?
Re: Cocoa and AudioUnits?
- Subject: Re: Cocoa and AudioUnits?
- From: Andy <email@hidden>
- Date: Tue, 21 Jan 2003 11:04:12 +0000
What I would like to see is some confirmation that Apple is going to
implement a cocoa API for Core-Audio. I have nothing against carbon,
but it is easier to call carbon from cocoa (when needed) than
vice-versa. I personally prefer cocoa to carbon for GUI code and when
given the choice I go for cocoa because my experience has shown that
development time is shortened by at the very least a factor of 2. I
have programmed Mac OS for more than 10 years and when I saw Obj C I
was initially horrified, and I believe that many Mac developers still
haven't got over that initial shock. But when you get into cocoa you
quickly realise all the benefits, and there are many.
The current core-audio GUI implementation might be OK if graphic
compositing wasn't broken, that is my main gripe and it's a big one.
Quartz is slow enough already, but in AudioUnits it seems we are
required to implement unnecessary hacks to layer alpha'd controls.
Those hacks often require parts of the same graphic to be drawn at
least twice, slowing things down even further. I also prefer cocoa's
invisible event handling, the carbon event model is clumsy in
comparison.
Come on guys at Apple, yes Bill I know you told me you don't want to
talk about this! But it's about time we had confirmation. Everywhere
else in the OS we have a choice, Carbon or Cocoa, but in core-audio we
are being forced to use (IMHO ) a broken model. Please give us the
choice. Carbon for legacy, Cocoa for new.
_______________________________________________
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.