Gentlemen, I'm not a moderator, but I'm _sick_ of this argument. Can we please not have it again?
--Kyle Sluder On Thu, Sep 13, 2012, at 03:53 PM, Graham Cox wrote: > > On 14/09/2012, at 5:45 AM, James Merkel <jmerk...@mac.com> wrote: > > > So unless I'm missing something, sandboxing is a piece of cake. > > > Congratulations, your app uses the file system in a simple way, and in > the way that was largely anticipated by the sandboxing design. > > It's when you have slightly unusual requirements that things get tricky. > If you want to retain access to a file you opened across relaunches of > your app, sandboxing will prevent that without special steps being taken. > If you want to use the Save dialog to save a file WITHIN your sandbox, > you can't. If you need access to files whose paths or URLs you create > programmatically (e.g. you select a file.foo but it has a counterpart > file.bar that you also need to access) you can't... > > These are the sorts of issues that have caused so much grief, not the > simple ones you mention. > > --Graham _______________________________________________ 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
