Effects of MacOS Sandbox on Igor 7

I am growing curious about how sandbox requirements under MacOS 10.7 and beyond will affect the ability of Igor 7 to communicate with external apps, for example via ExecuteScript. What should we start thinking about to change because it is already clear will break under Igor 7? What alternatives might exist to replace missing functions or options? I suggest this as a place to post a discussion to the general topic.
It is my understanding that there should be little to no effect such that Igor properly asks the OS for the resources it needs.
mtaylor wrote:
It is my understanding that there should be little to no effect such that Igor properly asks the OS for the resources it needs.


I have had one case (Goalscape) where the response to my request to support running scripts was answered as follows:

Quote:
Unfortunately this is not possible, since scripts cannot run on the OS level outside the application sandbox. Moreover, any special URL protocols must be first registered in the OS to invoke any such operation via an embedded URL.


This suggests to me that Igor (or indeed any other application) will no longer be able to use ExecuteScript to spawn a shell or Applescript as an external process to itself.

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAHuntsville
FWIW, Apple has reported on how scripting is to be handled in Mountain Lion. All seems to me to be better than perhaps expected. My interpretation after a quick read on the handouts (sans voice-over talking) is, apps and/or users need only provide the proper security certifications/entitlements for/to their apps/scripts. See the posting from Session 206 of the WWDC ...

https://developer.apple.com/videos/wwdc/2012/?id=206

Also, my first read about this news originated from OmniGroup, as noted here ... http://forums.omnigroup.com/showthread.php?t=24621

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAHuntsville