Re: Cross-platform?
Re: Cross-platform?
- Subject: Re: Cross-platform?
- From: John Stiles <email@hidden>
- Date: Wed, 15 Feb 2006 16:42:24 -0800
On Feb 15, 2006, at 4:30 PM, Camillo Lugaresi wrote:
On 16/feb/06, at 01:04, Scott Squires wrote:
Curious about how people are dealing with cross-platform issues.
Cocoa on Mac to ? on Windows, ? on Linux.
If it was a carbon app all/most code would be in C or C++ and UI
could be
dealt with in at least somewhat similar fashion between
platforms. Seems to
be one of the potential trade-offs of Cocoa vs Carbon that Apple
doesn't
address much.
I know I can code in C or C++ within Cocoa as well but how are
most real
Cocoa developers dealing with this and the UI porting issues? Or
are most
Cocoa developed apps staying Mac only?
Is the potential faster/easier coding in Cocoa(is it?) offset by
added time
and work to port to other platforms?
A common practice is to write the Mac front-end in Cocoa and the
cross-platform back-end in whatever. This is no different from
writing the front-end in Carbon: in both cases, it's not portable
and you need to write a different front-end for other platforms.
Another strategy is to use a cross-platform toolkit for the GUI,
but this usually results in a sub-optimal user experience on the
Mac. A recent example of this approach is Google Earth.
From personal experience, I can say that C++ back-end plus Cocoa/
Objective-C front-end is a great way to develop an app. A little bit
of forethought is needed to keep the front-end and back-end truly
separate, but that's true whether you use Cocoa, Carbon, or a
separate approach. There are adaptors to let STL containers work as
NS containers as well; I haven't tried these personally, though.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden