I had a vaguely similar requirement in that I wanted to port my Windows app to
Cocoa and I wanted to do it (and indeed did do it) by writing a 'Windows
emulation library' on top of Cocoa. This took about a year.
To get started, I wrote a very simple one-window Cocoa program ('Cocoa
Testbench') using the 'Cocoa application' template in Xcode. While this
involves getting to grips with Interface Builder it provides a shortcut to
having something you can experiment with on an ongoing basis, and knowing IB is
a useful skill anyway. And I have a bit of good news for you: Cocoa is very
hackable, once you get into it. My initial fear that it was just a high-level
RAD tool went away quite quickly.
I also found reading up on Objective-C very valuable. It is more subtle than
at first appears. I found Apple's online documents more than adequate for
this. Other than that, I can only echo the advice given by others: buy a
couple of 'get you started' books (Hillegass is very readable) and be prepared
to invest quality time in learning the Cocoa framework. You can probably
ignore Core Data and KVO though, at least at first. I did, and, for what I am
doing, I do not miss them. Tell you what though; taking in so much new
material is very tiring, mentally. Get plenty of sleep and forget everything
you know about Carbon.
Paul Sanders.
----- Original Message -----
From: "Bill Appleton" <billapple...@dreamfactory.com>
To: "Michael Ash" <michael....@gmail.com>
Cc: "cocoa-dev" <cocoa-dev@lists.apple.com>
Sent: Friday, April 23, 2010 3:08 PM
Subject: Re: NSApplicationMain question
hi all,
wow thanks for the advice. i agree i will need to ultimately know a lot
about cocoa to make the transition
i don't have a lot of choices, in that the engine i am porting is about 1/2
million lines of C, and about 10,000 enterprise companies depend on it,
mainly on windows, although a significant number of them have macs
so i have made a lot of efforts to learn cocoa, but our product is an NPAPI
browser plugin, so we have to switch from carbon windowrefs to cocoa
nswindows because that is what the NPAPI interface provides. in fact much of
the architecture is dictated by this interface which runs under WebKit /
Safari / Firefox.
so its a "real world" scenario instead off the best of all possible worlds
but its great to meet so many knowledgeable people, i'll have some more
tangible questions as this progresses
thanks,
bill appleton
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
