Hi All, Not sure I understand all the issues but this should be good news for Cocoa lovers:
1) When Safari runs as 64 bit it loads and runs a 32 bit or 64 bit Cocoa NPAPI plugin just fine. The 32 bit version of Safari will only run 32 bit NPAPI plugins. 2) The exact same 32 bit plugin for Safari will work great in FireFox 32, although you need to ask for the Carbon Event model. That is pretty amazing -- FireFox hasn't released a Cocoa version yet! 3) The FireFox 64 bit release candidate (minefield) runs the 64 bit version just great. I'm not sure if 64 bit firefox will run a 32 bit plugin, I will find out. At runtime there is nothing strange going on anymore since they fixed these bugs. You are running on the main thread in your own process. NPApp is initialized for you. Actually the "out of process" security thing is really cool, it is a more isolated & predictable environment for us to run in. Best, Bill On Tue, Jun 22, 2010 at 2:07 PM, Jens Alfke <j...@mooseyard.com> wrote: > > On Jun 22, 2010, at 2:02 PM, Charles Srstka wrote: > > > Unless your plug-in is 64-bit only, there’s the chance the 32-bit binary > could load into a non-Cocoa browser such as Firefox. > > I’m not sure Chrome is 64-bit yet, but it probably will be soon. Using > AppKit in a Chrome plugin will crash and burn since it will be running in a > sandboxed background process with no real AppKit environment. > > —Jens _______________________________________________ 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
