Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Reduce launch times for AppleScript apps on Intel' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Reduce launch times for AppleScript apps on Intel
Authored by: wordtech on Aug 07, '06 07:31:01AM

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.

I realize one can use AppleScript Studio to work around this, but ASS is usually overkill for my needs.



[ Reply to This | # ]
fixing the application name for compiled AppleScripts
Authored by: hayne on Jan 05, '07 10:54:36AM
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.

[ Reply to This | # ]