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


Click here to return to the 'Re: Fix iChat AppleScripts in Mountain Lion ' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Re: Fix iChat AppleScripts in Mountain Lion
Authored by: Uncle Asad on Aug 24, '12 07:36:49PM

Compiled AppleScripts (every type of AppleScript with an extension other than .applescript) are saved as, well, compiled “code” rather than the text you type. For commands, properties, and so forth, the pieces of the script are compiled into the appropriate Apple Event signature. When Script Editor opens a script, it “decompiles” the Apple Events back to human-readable text (whereas when running the scripts, those Apple Events are just sent to apps).

References to applications themselves are stored in a couple of ways in compiled scripts, including by path and by creator code. It’s possible this has been changed/expanded in newer OS versions (to use bundle identifier rather than creator code, for instance), but the creator code app reference is what allows Script Editor to pick up on app name changes like the “iCal” to “Calendar” change you saw.

All of which is a long way of saying that perhaps Messages has a different creator code or bundle id from iChat, whereas iCal and Calendar both share the same code/id. Since Messages is in some ways a “new” app while Calendar is just a simple name change, it would not be unreasonable for Messages to get a new creator code and bundle id.



[ Reply to This | # ]
Re: Fix iChat AppleScripts in Mountain Lion
Authored by: pbeyersdorf on Aug 26, '12 10:31:54PM

Thanks for the explanation. This makes sense now.



[ Reply to This | # ]