Re: Isolated process for each NSDocument of my app
Re: Isolated process for each NSDocument of my app
- Subject: Re: Isolated process for each NSDocument of my app
- From: Kyle Sluder <email@hidden>
- Date: Fri, 14 Jun 2013 08:01:21 -0700
On Jun 14, 2013, at 1:15 AM, Daniele Margutti <email@hidden> wrote:
>
> No offence guy, but seriusly I can’t. We have a compatible UIKit layer which can run on OS X. In order to mantain compatibility I need to handle UIApplication and UIScreen singleton; morehower I need to manage UIAppearance. This thing can’t work on with multiple projects at the same time so in order to work with it I need to isolate each project/UIKit instance/process from the other.
So your response to a problem entirely of your own making is to try to whip a system framework into doing something it is very much not designed to do.
Step back and take a deep breath. You need to remove your blinders and rationally analyze your options.
AppKit simply does not and will not work the way you want it to. You can't just split code into subprocesses when that code might be sharing untold amounts of state and memory. It would be *astronomically* more difficult to accomplish this than it would be to 1) either fix your UIKit clone or 2) just stop treating the Mac as a second-class citizen and use AppKit natively for your UI. Both of those are under your control; the code within AppKit is not.
--Kyle Sluder
_______________________________________________
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