On Jun 13, 2013, at 3:52 AM, Daniele Margutti <m...@danielemargutti.com> wrote:
> In this case each process is isolated from the others as like with Safari. > What’s the best way to accomplish it on OS X? There is no [public] support for running parts of the GUI of an app in separate processes. It requires things like sending events over IPC and maintaining shared-memory window/view buffers. I’m somewhat familiar with the way Chrome does it, having worked on Chrome for a few years, and it is very complex and messy. (You can check out the Chromium source and look through it if you want.) I’m sure Safari’s implementation is too, unless they’re using some hypothetical private AppKit APIs for cross-process events/views. The short answer is that this would be very difficult to do, and you’ve have to become intimately familiar with XPC, the low levels of AppKit event handling, CoreGraphics, shared memory, etc. etc. On the plus side, if you accomplished it and made it into a reusable framework, you’d be a hero. —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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
