Carbon or not?

A_SN · A_SN #1 (**permalink**)

04-05-2009, 11:14 AM

As some of you may know from my other semi-related thread, I'm a Windows developer and I've set out to port my commercial Windows program to Mac OS X. It's entirely written in C, and the overwhelming majority of the code is platform independent, and using a bunch of open source libraries for that (SDL, Allegro, DevIL, libsndfile, libmpg123..). The problem I'm facing is knowing what to replace the few Windows API calls with, and how to deal with the aspects unique to Mac OS X, e.g. the menus.

The Windows API calls consist in pretty simple stuff, such as a function to pop up an Open dialog, same for a Save dialog, a function to detect how many CPU cores we have (that one's probably in POSIX), a function to copy an image to clipboard.. My program being entirely in C, according to what I've recently read, I should aim to replace my WinAPI calls with Carbon API calls, correct? But here's the problem, I've also read that apparently Carbon is already old and being pushed out, that "it is not a good idea to write new applications using Carbon", and that you can't even build 64-bit apps with it.. Doesn't sound any good to start porting to it against all recommendations..

But on the other hand, what other choice is there? Surely a pure C program can't use Cocoa? What else is there? Or is Carbon a decent choice for the little I need?

louishen · louishen #2 (**permalink**)

04-05-2009, 11:37 AM

You might want to post that thread in the Apple developer forums as well

Apple - Support - Discussions - Developer Forums

A_SN · A_SN #3 (**permalink**)

04-05-2009, 11:46 AM

Quote:

Originally Posted by louishen

You might want to post that thread in the Apple developer forums as well

Apple - Support - Discussions - Developer Forums

Oh thanks, just done

xstep · xstep #4 (**permalink**)

04-05-2009, 03:19 PM

You'll definitely get great answers from the Apple developer forums.

Sounds like you have some code separation between the underlying C code and your GUI presentation code. Given that, I think you'll find using XCode and Interface Builder a fine solution which is also the long term solution. Apple has effectively announced the death of Carbon.

There is one blog out there by a guy who compares Windows and Cocoa coding & ideas. Unfortunately, for the life of me, I can' remember it. It is something I run a cross via other sites linking to it.

xstep · xstep #5 (**permalink**)

04-19-2009, 02:17 PM

Quote:

Originally Posted by xstep

There is one blog out there by a guy who compares Windows and Cocoa coding & ideas. Unfortunately, for the life of me, I can' remember it.

Here it is COCOA [The .NET Addict's Blog]. I've linked specifically to the Cocoa tag as there are other things there.

DairyKnight · DairyKnight #6 (**permalink**)

04-27-2009, 11:04 AM

You can mix C with Objective C code. Cocoa is a better choice.

louishen #2 (permalink)
Member Since: Oct 22, 2007 Location: London Posts: 8,657 Mac Specs: Mac Mini Core i7 2012 \| White 2009 MacBook 2 Ghz \| 733 Mhz G4 Quicksilver	04-05-2009, 11:37 AM You might want to post that thread in the Apple developer forums as well Apple - Support - Discussions - Developer Forums Member of the Month September 2008 & August 2012 \| Found advice useful? – use the rep system
	QUOTE Thanks

xstep #4 (permalink)
Member Since: Jun 25, 2005 Location: On the road Posts: 3,231 Mac Specs: 2011 MBP, i7, 16GB RAM, MBP 2.16Ghz Core Duo, 2GB ram, Dual 867Mhz MDD, 1.75GB ram, ATI 9800 Pro vid	04-05-2009, 03:19 PM You'll definitely get great answers from the Apple developer forums. Sounds like you have some code separation between the underlying C code and your GUI presentation code. Given that, I think you'll find using XCode and Interface Builder a fine solution which is also the long term solution. Apple has effectively announced the death of Carbon. There is one blog out there by a guy who compares Windows and Cocoa coding & ideas. Unfortunately, for the life of me, I can' remember it. It is something I run a cross via other sites linking to it. CameraTime - Time lapse photography for novice and advanced users. When asking questions, post the version of your software. You'll receive better answers. Please post your results to the thread as it is good feedback.
	QUOTE Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Carbon framework on XCode	Rafi Shalom	OS X - Development and Darwin	1	04-17-2008 01:14 PM
Ways to tell the difference between a Cocoa app and a Carbon app	remain	OS X - Apps and Games	0	05-22-2007 08:55 AM
Silver Carbon Macbook	manguyen	Schweb's Lounge	22	03-03-2007 06:47 PM
LMSetWindowList() replacement in Carbon	presenter	OS X - Development and Darwin	0	06-22-2005 05:07 AM
Javascript crashes IE 5.2.3 on Mac OS X	alatoum	Web Design and Hosting	2	05-12-2005 04:23 PM

Carbon or not?

Internet Services

Web Development

Digital Marketing

Consumer Tech

A_SN #1 (permalink)
Member Since: Apr 02, 2009 Posts: 6	04-05-2009, 11:14 AM As some of you may know from my other semi-related thread, I'm a Windows developer and I've set out to port my commercial Windows program to Mac OS X. It's entirely written in C, and the overwhelming majority of the code is platform independent, and using a bunch of open source libraries for that (SDL, Allegro, DevIL, libsndfile, libmpg123..). The problem I'm facing is knowing what to replace the few Windows API calls with, and how to deal with the aspects unique to Mac OS X, e.g. the menus. The Windows API calls consist in pretty simple stuff, such as a function to pop up an Open dialog, same for a Save dialog, a function to detect how many CPU cores we have (that one's probably in POSIX), a function to copy an image to clipboard.. My program being entirely in C, according to what I've recently read, I should aim to replace my WinAPI calls with Carbon API calls, correct? But here's the problem, I've also read that apparently Carbon is already old and being pushed out, that "it is not a good idea to write new applications using Carbon", and that you can't even build 64-bit apps with it.. Doesn't sound any good to start porting to it against all recommendations.. But on the other hand, what other choice is there? Surely a pure C program can't use Cocoa? What else is there? Or is Carbon a decent choice for the little I need?
	QUOTE Thanks

DairyKnight #6 (permalink)
Member Since: Apr 27, 2009 Posts: 3	04-27-2009, 11:04 AM You can mix C with Objective C code. Cocoa is a better choice.
	QUOTE Thanks

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)