Re: Applescript in the future
Re: Applescript in the future
- Subject: Re: Applescript in the future
- From: Shane Stanley <email@hidden>
- Date: Thu, 23 May 2013 08:42:26 +1000
On 22/05/2013, at 11:10 PM, Chris Swain <email@hidden> wrote:
> To give a real example I have a FileMaker database containing chemical structures, I have FileMaker script that takes a text description of a molecule from a database field, then uses the run applescript function within FileMaker to pass the data to chemical computation application that calculates a number of properties. The script then calls a graphing application that creates a series of plots which are then imported into database fields.
I presume Chris Nebel will correct me if I'm wrong, but this is one of the few cases where sand-boxing could have any real impact on scripting. If the scripts target another app they will need to be in separate script files, stored in a particular folder on the user's startup disk.
That's assuming FileMaker is ever sand-boxed. And if it is, I suspect there would also be limits on what you can do with FileMaker's own scripting, especially in terms of exporting files. I could see that being more of an issue for a lot of users -- and AppleScript might be a good workaround.
--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>
_______________________________________________
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