[...] We were hoping to solve this for the time being by checking in the sdef into source control. If future versions of our products use a static sdef, this wouldn't be an issue if we could just hand this sdef off to osacompile. Then the app wouldn't need to exist before [...]]]>
[...] I don’t think this is possible, but would be happy to be wrong. I don’t have a situation where I need to build headlessly, but I do have 2 situations in which it would be nice to do this: 1) Chicken and egg problem where building automator actions for [...]]]>
Hi all, Now that AppleScript no longer requires a WindowServer connection, and static sdefs can be used for terminology without launching their containing app, we're once again attempting to build our Automator actions as part of our build process. Unfortunately, osacompile [...]]]>
Title: OSACompile preventing double-clicking on files in finder t if i first execute: defaults write com.victor.jeeves NSScriptingDebugLogLevel 1 and then in my app, i execute the following: ComponentInstance ci = OpenDefaultComponent( kOSAComponentType, typeAppleScript); [...]]]>