Re: NSApplicationMain question
Re: NSApplicationMain question
- Subject: Re: NSApplicationMain question
- From: Michael Ash <email@hidden>
- Date: Thu, 22 Apr 2010 21:39:39 -0400
On Thu, Apr 22, 2010 at 6:45 PM, Bill Appleton
<email@hidden> wrote:
> hi all,
>
> thanks for the great advice
>
> for better or worse i am porting a large piece of enterprise software from
> carbon/windows to cocoa/windows
>
> most of the code is platform independent, but i can't make big changes to
> the overall structure of the program
>
> so like step one is to replace WindowRef with NSWindow and watch the carnage
> ensue
Step one should be to actually learn Cocoa.
You seem to think that because you're going to be just swapping in
Cocoa for Carbon that you don't really need to know a lot about how
Cocoa works. In fact, precisely the opposite is true. If that's going
to be your strategy, you need to know *more* about how Cocoa works
than the average Cocoa programmer. Cocoa makes it easy to build
conventional Cocoa apps, and you can often get away with not knowing
all that much about how stuff works internally. But your proposed
approach is highly unconventional. To succeed, you'll need to have a
good understanding of how Cocoa works on the inside. In short, you
need to know the rules extremely well before you start breaking them.
Others have already addressed the merits of your proposed approach. If
you decide to go with it anyway (and I can understand the temptation)
then you'll probably want to take a time out, get a book or three on
Cocoa, build a small test application and then expand it until you
have something that exercises a decent fraction of the framework, and
*then* come back and start doing your conversion.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden