Re: NSSavePanel: Another sandbox issue
Re: NSSavePanel: Another sandbox issue
- Subject: Re: NSSavePanel: Another sandbox issue
- From: Alex Zavatone <email@hidden>
- Date: Thu, 31 May 2012 17:43:02 -0400
On May 30, 2012, at 10:54 PM, Marco S Hyman wrote:
>> 3. When I use -setDirectoryURL: and the URL is somewhere in my sandbox, the actual URL displayed is the old location, back in ~/Library/Application Support (!)
>
> When using a sandbox in Mac OS X 10.7 and later, the home directory is the
> app’s container directory. That is
>
> ~ ==> /Users/<user>/Library/Containers/<app>/Data/
>
> Now the fact that the application is sandboxed and lives in a container
> is irrelevant to the user. Try taking off your developer hat and
> putting on your dumb user hat. A user will want to save somewhere,
> perhaps in his Documents directory. In a sandboxed app that will be
> /Users/<user>/Library/Containers/<app>/Data/Documents/
So, before I start waving my hands in the air, running around the office and panicking, does this mean that the user can not save files where ever he/she wants to on the HD in future versions of the Mac OS?
> The user doesn't know or care what the actual path is. Why are you
> trying to show it in a save dialog.
>
> Marc
Sometimes, the user does.
If sandboxing ALLOWS the user to save in a private special place but PREVENTS them saving files where they choose, then this is a scary path.
I certainly hope this is not the case.
In all of Apple's success, I see the openness and fun to use nature of the Mac platform running away right in front of us.
_______________________________________________
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