Re: Applescript in the future
Re: Applescript in the future
- Subject: Re: Applescript in the future
- From: Christopher Nebel <email@hidden>
- Date: Wed, 22 May 2013 10:45:02 -0700
On May 22, 2013, at 5:10 AM, Shane Stanley <email@hidden> wrote:
> On 22/05/2013, at 10:06 PM, Alex Zavatone <email@hidden> wrote:
>
>> So, that means that you can't tell an app anything because of Sandboxing, right?
>
> Wrong. It means a sand-boxed app can't send Apple events to another app.
And even that's overstating things -- a sandboxed app can't send Apple events to another app *if it doesn't have entitlements to do so*. The default sandbox doesn't allow sending Apple events to any other app, true, but the default sandbox doesn't allow using the network either, and you don't hear anyone complaining that Apple is deprecating the Internet.
Basically, for 99.9% of apps, this just isn't an issue -- there are mechanisms to let them do what they need. For the 0.1% that do have issues with sandboxing (as currently implemented), it means they can't be in the Mac App Store, but not that they're out of business. And by the way, this was all covered at WWDC 2012, so refer this benighted developer to the "Secure Automation Techniques in OS X" session.
--Chris Nebel
AppleScript Engineering
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden