On May 22, 2013, at 11:30 AM, Alex Zavatone <email@hidden> wrote:
On May 22, 2013, at 1:45 PM, Christopher Nebel wrote: 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.
So, yeah, I was being sarcastic in my original reply, but this sandboxing is just onerous and places annoying and expensive implications on the developers. ...
Look, when you're the developer on your own box and you are THE admin, and you're trying to push a multi million dollar product on multiple platforms you DO NOT WANT to have to worry about any of this sandboxing garbage.
PERIOD.
First off, I'm gratified that you used AppleScript and AppleScriptObjC for a project like that. (Can our marketing director quote you? Yes, I'm serious.)
However, to your point: you don't want to deal with sandboxing your projects? Then don't. Really, it's fine. Nothing in Mountain Lion requires that applications be sandboxed. Nothing about your FiOS application would have to change in Mountain Lion. Some of the applications it talks to might be sandboxed, but that doesn't affect their scriptability. Worst case, you might need to sign your application, but that's a no-coding-involved change, and is mostly for convenience.
People seem to get this idea that sandboxing is all-pervasive, and it's really not. Being in the Mac App Store requires being sandboxed, because apps there are held to specific standards. Outside of that, though, you're still free to go as nuts as you like.
--Chris Nebel AppleScript Engineering |