|
|
10.4: Reduce launch times for AppleScript apps on Intel
This is just plain goofy--anyone know why Apple has made AS application bundles universal but not applets? There are sometimes valid reasons to prefer an applet over an application bundle, particularly if you are executing a command as an administrator. When you execute "do shell script foo with administrator privileges" under an applet (standalone script), you are presented with a dialog that includeds the correct name of your applet ("mycoolscript.app requires you to enter your password"). With an application bundle, the actual executable (in mycoolscript.app/Contents/MacOS) is called "applet," and you get this dialog: "applet requires you to enter your password." Not very polished.
fixing the application name for compiled AppleScripts
You can fix this problem (that all AppleScript apps compiled into an application bundle have "applet" as the executable name) by using my Bash script 'fixAppleScriptApp'
(available from: my Bash scripts page)
This script modifies the application bundle so that the executable is named the same as the .app It also provides the option to change the "creator code" or "signature" of the compiled AppleScript application. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|