Amen.
Codewarrior is dead, long live Xcode. (I still mourn CodeWarrior, but
what's past is past.)
I did some work with MFC a couple of years ago, and thought it was
pretty nice (not elegant, but productive). Now, I am trying to port
my Cocoa app to Windows, and for various reasons decided to go with
MFC again. I cannot believe how much of a pain it is. I just learned
some Cocoa/ObjC for my last project, and it was easier to learn Cocoa/
ObjC than to get this thing going in MFC/C++.
Get the "Objective-C 2.0 Programming Language" pdf from Apple, and
have it printed out at Kinkos, and BUY A COPY OF "Cocoa Programming
for Mac OS X, Third Edition" by Aaron Hillegass. While there is a
learning curve for Cocoa/ObjC, once you get going you will look back
at MFC with disdain.
Refactor the MFC project FIRST. Seperate the UI from the logic as
much as possible. It should help you understand the MFC code better,
and you might even be able to stick some of it in a dynamic library
for reuse.
On Oct 30, 2008, at 11:21 AM, [EMAIL PROTECTED] wrote:
***DO NOT*** expect that it's merely a matter of finding the
corresponding
Mac API call for each Windows API call--the differences run deeper
than
that. In order to be successful, you ***WILL*** have to learn to
be a Mac
developer, period, no shortcuts.
Don't let that scare you. It's easier than you think. And in the
end, you'll go back to Win32 grumbling about how much extra work
you have to do there. ;)
_______________________________________________
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 [EMAIL PROTECTED]
