In fact, you should rush right out and by both of those books right
away! (ok... maybe not)
The rest of the Carbon books are hopelessly out-dated.
Jim
On May 30, 2006, at 1:13 PM, Davy Durham wrote:
Greetings,
I am wanting a recommentation of book(s). I'm an experienced C/C+
+ programmer and have done GUI application development in win32
and linux. I'm venturing out into the OS X world and would like
to know if you can recommend any good books.
In general it is true that there are no third party books, but you
can find some helpful information at Apple's web site.
Right at the top you'll find an overview of Carbon features, as well
as guides for porting Windows and Linux software. Even if you aren't
concerned with a porting task right now those guides might offer you
some insight into what you'll have to look out for.
Pay particular attention to the Carbon Event Manager and the HIView
programming guide. Those are fundamental technologies and a strong
grounding in those would be very helpful.
Another good thing to look at is the legacy interfaces guide at:
This will give you some idea of which technologies to AVOID. If you
start reading about one of these, you may be chasing down the rabbit
hole of legacy software.
What I don't want to do is just learn the Carbon API and assume I
can write a good application for OS X by simply doing what I've
done in win32 or linux.
Some of the ideas and concepts will carry across just fine. For
example, carbon events are similar to Win32 Windows messages (i.e.
WM_PAINT). Some of your Linux/Unix experience may be helpful if you
want to do multiprocessing or networking. However some concepts will
be completely new.
In general Macintosh users are much more particular about look and
feel and application behavior issues than Win32 or Linux users. If
you want to create a well-received, successful Mac OS X application,
you should carefully look at the Aqua Human Interface guidelines.
I'm plenty familiar with HOW to program, but would want to read a
book that informs on how things are generally done in the OS X
world. I realize that there is also Cocoa, but want to stick with
Carbon for the time being.
I understand the sentiment. I would, however, recommend that you
eventually spend a day or two looking at Objective-C
While Carbon itself does not use Objective-C, and it's possible to
create a Mac OS X application that does not use Objective-C, many of
the more interesting recent technologies to come out of Apple do have
Objective-C interfaces.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
