Re: Cocoa Cross Development
Re: Cocoa Cross Development
- Subject: Re: Cocoa Cross Development
- From: Chris Hanson <email@hidden>
- Date: Mon, 3 Nov 2003 15:45:25 -0600
On Nov 3, 2003, at 2:33 PM, John Nairn wrote:
2. Shouldn't one always cross-develop back to 10.1? What's the point
of limiting audience for a program. Does cross development make the
application bigger or slower or have some other deleterious effect
such as slower compilations?
There are a ton of features in Mac OS X 10.2 that aren't available in
Mac OS X 10.1.
There are a ton of features in Mac OS X 10.3 that aren't available in
Mac OS X 10.2.
Some of these features can give your application more functionality.
Some of these features can reduce your development time.
If you want to produce an application that takes advantage of new
features, it has to target the new operating system. For instance, if
you want to build an application that uses Rendezvous, you have to
target at least 10.2; Rendezvous doesn't exist on 10.1. If you want to
build an application using NSController, you have to target at least
10.3; NSController doesn't exist on 10.2.
The one downside of the way Cocoa and Mach-O are structured on Mac OS X
is that it's not trivial to build applications that make use of new
features when available, but don't when they're not. This is something
that is done very well in Carbon (and InterfaceLib) with CFM via
weak-linking and the Gestalt() call. I wish the same mechanism were
available in Cocoa.
-- Chris
--
Chris Hanson, bDistributed.com, Inc. | Email: email@hidden
Outsourcing Vendor Evaluation | Phone: +1-847-372-3955
Custom Mac OS X Development | Fax: +1-847-589-3738
http://bdistributed.com/ | Personal Email: email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.