Re: NSApplicationMain question
Re: NSApplicationMain question
- Subject: Re: NSApplicationMain question
- From: Bill Appleton <email@hidden>
- Date: Fri, 23 Apr 2010 07:08:46 -0700
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
On Thu, Apr 22, 2010 at 6:39 PM, Michael Ash <email@hidden> wrote:
> 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
>
_______________________________________________
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