Re: Follow up to CocoaUI question...
Re: Follow up to CocoaUI question...
- Subject: Re: Follow up to CocoaUI question...
- From: Richard Burnett <email@hidden>
- Date: Thu, 25 Jan 2007 12:41:19 -0800
Thanks for the response!
I think the thing that started me most was CocoaUI's not being supported in hosts, I just wasn't even aware that was an issue altogether. If I had known, I'd have started with Carbon instead. The biggest problem with all this is that I am not a very heavily experienced OSX programmer. I've used WindowsAPI, MFC, OWL, DirectX and even some stuff in linux with GTK++ and LADSPA plugins. I instantly latched on to the CocoaUI stuff because it is VERY easy to write with and control the GUI.
Carbon...in simple terms...is not. It's much more like WindowsAPI it appears in how it handles things and what you have to do with it.
I wish that one of the sample examples that came with Xcode had a Carbon UI done in the interface builder and NOT creating the window from scratch. This is where I am having trouble because I have no example of how to do this.
I tried downloading all the AU example SDK libraries that others have created, however, these are done with much older versions of xcode (or pb) and either don't compile, or if I manage to fix up the code so they do, don't execute properly (wrong compiler options) AND THEN do not pass AUVAL. So I am left not having a good example of what it is that I am trying to do and getting quite overwhelmed while trying to learn at the same time.
I've written the makers of a few of the SDK's to see if they could release a version compiled with 2.4.1 and start from there. What I really just want is a project of a simple audio effect with a carbon interface done with the interface builder and all connected together. Most of the issue here, again, is me and where I am coming from.
Rick
On Thursday, January 25, 2007, at 01:14PM, "Justin Carlson" <email@hidden> wrote:
>Hi Rick,
>
>I am certainly not the authority on this, but I'll jump in the
>discussion since it is of high interest to me.
>
>> So it appears that Digital Performer 5.11 does not support CocoaUI
>> views. I've put in some code to check what it calls and I never see
>> it ask anything about a CocoaUI. At this point I am not sure what to
>> do. All the plugins I use work in Digital Performer, does this mean
>> they are all written with Carbon?
>
>Probably. I am primarily a Cocoa programmer as well, so you had
>better wait for a definitive answer from the Carbon gurus. Perhaps
>there is a way around it.
>
>> What I am trying to decide at this point is how to proceed. I just
>> spent a week putting together my UI in Cocoa...do I start my App over
>> as a Carbon AU? What would be the suggestion to move the GUI into a
>> format that is supported in more host applications?
>
>If you seek a larger community, use Carbon. Hosts which handle Cocoa
>UIs best are Cocoa apps ( unsurprisingly ) - AU Lab, GarageBand,
>Audiofile Engineering's line, etc. If you ask me, Carbon is king.
>
>Hopefully somebody with much experience in this topic will join the
>conversation. auguiFramework ( at sourceforge )may help you get on
>track with a Carbon UI. A few developers have used Cocoa UIs with
>their shipping plugs - maybe you can to contact them if you are still
>interested in Cocoa. If I were developing a professional series of
>commercial plugins today, I would choose Carbon. If I had the time, I
>would explore Cocoa possibilities before settling on Carbon.
>
>J
>
>
>
>
>___________________________________________________________
>All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
>http://uk.docs.yahoo.com/nowyoucan.html
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Coreaudio-api mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
>
>This email sent to email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden