Re: PICT control problems [SOLVED]
Re: PICT control problems [SOLVED]
- Subject: Re: PICT control problems [SOLVED]
- From: Bill Bumgarner <email@hidden>
- Date: Sat, 24 Jun 2006 10:28:21 -0500
This is starting to go afield of Xcode-users on-topic....
On Jun 24, 2006, at 9:45 AM, John Lunt wrote:
On 24 Jun 2006, at 14:55, Markus Hitter wrote:
Am 23.06.2006 um 22:31 schrieb John Lunt:
The Xcode documentation seems to spend 75% of its time explaining
how to port your code from other versions/frameworks/platforms,
but seems quite "diffused" for people who just want to write a
modern Carbon app from scratch.
To some extents this reflects Apple's recommendation to write new
apps using Cocoa.
Yeah, I thought hard about this, but decided to go with Carbon for
2 main (and personal) reasons.
1. Cocoa is a bit of a niche - which is fine if you are doing it
full-time but this is my hobby, so I (personally) don't want to
learn something of limited applicability elsewhere.
I'm not sure I understand the reasoning here. Any system that can
run a Carbon app will also be able to run a Cocoa app, save for the
last remaining handful of people still running Mac OS 9. As such,
Cocoa is no more of a niche than Carbon.
For new development on Mac OS X, you should generally use Cocoa.
Carbon isn't going away any time soon, but it also isn't the target
for new technologies and frameworks, either.
As well, you generally have to write a lot less code to get the same
basic stuff done in Cocoa vs. Carbon.
2. My day job involves programming in C/C++ on windows (but I'm not
a professional programmer), so I've got quite a lot of experience
to fall back on when I get stuck with a C app. What I'm missing is
a good road map.
Objective-C is trivial to learn for a C programmer. And you can use C
++ in Objective-C apps just fine.
The real challenge with programming for the Mac is to learn how to
use the Framework APIs. Carbon may actually be a bit easier to
learn for someone with a Win32 or similar background, but not by
much. Given the productivity boost -- especially for the casual
programmer -- of Cocoa, the slightly longer learning curve is a wash.
C++ is a much larger set of conceptual and syntactic extensions to C
than Objective-C. As a result, it is much easier to augment and
automate the development workflow for Objective-C developers than it
is for C++ developers. Xcode's feature set reflects this.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden