Re: Cocoa and AudioUnits?
Re: Cocoa and AudioUnits?
- Subject: Re: Cocoa and AudioUnits?
- From: Robert Abernathy <email@hidden>
- Date: Mon, 20 Jan 2003 21:22:45 -0700
First, let me say that I don't really want to get into the language
aspect of this. Really, I dislike all of the languages that Apple is
using. I suppose that I dislike Obj-C the least. One thing I might
say about languages is that there are some third party language
developers out there that believed Apple when they said Cocoa was the
future. They have invested effort in making their implementations work
with Cocoa. I think it would be pretty neat to toss together an
environment for doing prototyping based on PyObjC.
What I care about is the Cocoa library. If Apple gives me a way to use
this whole library only in Lisp, I'll use it. I might even use it if I
had to use Visual Basic.
I've looked at the SDK's from Airy and Urs. The are both nice, and I
really appreciate their contributions. The problem I have is that they
must be used through Carbon. (I know, pretty obvious.) Here's an
example of my problem- one of the things I have in mind is using an
NSOpenGLView to give the user some feedback as they configure. Can I
do this using Carbon? Easily? I really don't want to put an interface
on my AudioUnit. I want to use all that Apple has developed to really
enhance user experience/control. To me, that's the whole point of
doing this stuff in software.
I understand full well Apple's need to keep those strong audio
platforms and applications that they had under OS 9. I also think that
if this is all they do, they will lose the audio market. This isn't my
impression of what Apple is about anyway. My view of them has been
that they build systems that allow developers to change the way users
view and interact with computers. Back in 1985 when I got my first
Mac, "Carbon" did this. Now, it doesn't! Now it doesn't even compete
with Windows API's. The only GUI library I'd like to go back to less,
is Motif.
I don't see the relevance of the cross platform arguments. Carbon is
not more cross platform than Cocoa. If anything, it is easier to
structure an app using Cocoa to make cross platform development easier.
Mixing the Cocoa GUI with the cross platform C or C++ in applications
is pretty easy. Getting an AudioUnit to use all of the really nice
Apple GUI stuff isn't possible.
Someone help me out with Carbon developers being upset that Apple is
pushing Cocoa. That is Apple's stated goal! Carbon was supposed to be
there to let existing applications begin the migration path before OS X
was even released. If Apple is going to continue to be successful,
they need to continue to push the user experience. I hope that Mac
developers don't short-sightedly saddle Apple with having to support a
nearly twenty year old library design for the rest of its existence.
Thanks everyone for your feedback.
Rob
_______________________________________________
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.