On Fri, Oct 8, 2010 at 4:22 PM, Jason Slack-Moehrle <[email protected]>wrote:
> Hello All, > > I have a large app that uses Carbon. We know that Carbon GUI is not > available in 64-bit. > > I need to integrate Carbon and Cocoa so that I can replace the existing > Carbon GUI elements with Cocoa equivalents. Mostly Dialog Boxes, etc. > > I know that I need to write C-ACllable Wrapper Functions for the Cocoa > stuff that I need, but I am not sure how to identify what I need to do. > Given that (a) if you're calling Carbon UI functions, you already aren't writing code portable to other operating systems and (b) that Objective-C is a superset of C, there should be no need for wrapping Objective-C with C. Just use Cocoa classes where appropriate and compile the file as Objective-C. That's usually done by making the file extension .m, but you can also do it with a compiler flag. > > Example. I know that I will probably need to use NSOpenPanel and > NSSavePanel. So I need to write a C-Callable Wrapper for the parts of > NSSavePanel that I would use? Like: setTitle, setMessage, etc, etc? > > Or am I in to deep to what needs to be done and I don't need to be? > > A nudge in the right direction is appreciated. > > Best, > -Jason > > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/kenferry%40gmail.com > > This email sent to [email protected] > _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
