Hello,
On Wed, 16 Jan 2013 17:12:15 +, jonat...@mugginsoft.com wrote:
On 16 Jan 2013, at 15:50, Fritz Anderson fri...@manoverboard.org
wrote:
On 16 Jan 2013, at 3:52 AM, jonat...@mugginsoft.com
jonat...@mugginsoft.com wrote:
Py_SetProgramName((char *)[[scriptRunner launchPath]
On 16 Jan 2013, at 17:40, Quincey Morris quinceymor...@rivergatesoftware.com
wrote:
On Jan 16, 2013, at 09:12 , jonat...@mugginsoft.com
jonat...@mugginsoft.com wrote:
To be honest I rarely remember to call -fileSystemRepresentation.
The docs seem to indicate that its only purpose is to
On 16 Jan 2013, at 03:44, John Nairn j...@geditcom.com wrote:
Thanks. I watched the one on Seccure Automation Techniques in OS X. Near
the end it said exactly what I wanted to hear which is that application-run
scripts that target only themselves have no restrictions. So far it is half
On 16 Jan 2013, at 3:52 AM, jonat...@mugginsoft.com jonat...@mugginsoft.com
wrote:
Py_SetProgramName((char *)[[scriptRunner launchPath] UTF8String]);
If a char* is destined for the file system, you should be using
-fileSystemRepresentation, not -UTF8String.
I forget that all the time.
On 16 Jan 2013, at 15:50, Fritz Anderson fri...@manoverboard.org wrote:
On 16 Jan 2013, at 3:52 AM, jonat...@mugginsoft.com
jonat...@mugginsoft.com wrote:
Py_SetProgramName((char *)[[scriptRunner launchPath] UTF8String]);
If a char* is destined for the file system, you should be
On Jan 16, 2013, at 09:12 , jonat...@mugginsoft.com jonat...@mugginsoft.com
wrote:
To be honest I rarely remember to call -fileSystemRepresentation.
The docs seem to indicate that its only purpose is to replace abstract / and
. characters with OS equivalents.
On OS X this would have seem to
Thanks. I watched the one on Seccure Automation Techniques in OS X. Near the
end it said exactly what I wanted to hear which is that application-run scripts
that target only themselves have no restrictions. So far it is half true in my
app. I can run an AppleScript now without troubles. But
I have sandboxed an app that allows users to run scripts as a major feeature
(i.e., dealbreaker on sandboxing only answer is to delete this feature). I was
pleased that I can run AppleScripts fine through the sandboxed app from Apple's
Script Editor, but the user experience is much (much, much)
On 14 Jan 2013, at 17:50, John Nairn j...@geditcom.com wrote:
I have sandboxed an app that allows users to run scripts as a major feeature
(i.e., dealbreaker on sandboxing only answer is to delete this feature). I
was pleased that I can run AppleScripts fine through the sandboxed app from
On 14 Jan 2013, at 17:59, Mike Abdullah cocoa...@mikeabdullah.net wrote:
Go watch the sandboxing videos from WWDC this year. They cover automation
quite a bit, and all will be made much clearer.
You want session 206 - Secure automation techniques in OS X.
If you don't have access we
On 14 Jan 2013, at 11:50 AM, John Nairn j...@geditcom.com wrote:
The errorInfo dictionary has only NSAppleScriptErrorNumber = -43 and no other
details. I could not find this error number in a google search.
For what it's worth:
$ macerror -43
Mac OS error -43 (fnfErr): File not found
--
11 matches
Mail list logo
