Skip to content

Snow Leopard vs My Scripting Additions

My various Scripting Additions (XML Tools, XSLT Tools, Property List Tools and List & record Tools) are compiled for 32-bit Intel and PowerPC machines. With the advent of Snow Leopard, AppleScript Script Editor, applets and droplets run as 64-bit processes which causes my Scripting Additions to fail to load on 64-bit hardware.

In order to continue using my Scripting Additions, you need to run the AppleScript Script Editor, applets and droplets in 32-bit mode. This is done by using the Finder’s Get Info panel and then checking the 32-bit Model checkbox.

My scripting additions make heavy use of Carbon which is 32-bit only, so making 64-bit versions may be difficult. I don’t want to say I’ll never make 64-bit versions, but at this stage its not clear to me how to move forward.

UPDATE: This problem and solution also applies to JavaScript OSA.

6 Comments

  1. What a pitty. I found your XSLT OSAX to be a godsent. I am just about to develop an Applescript Studio App which uses it to get Google Analytics reports and convert them to KML to be displayed in Google Earth.

    Even if i have the App run in 32Bit Mode, it crashes under Snow Leo. Even the simplest AS Applet writes a 0 Byte output file and then crashes when doing:

    set outFile to transform XML file (myFolder & “AnalyticsGeoReport.xml”) ¬ using file (myFolder & “analytics.xsl”) ¬ saving as file (myFolder & “output.kml”)

    Would you want a crashlog?

    Thanks a lot for the OSAX Anyways!

  2. I was not aware of the crash. I can reproduce it here using examples from the XSLT Tools dictionary.

    I’ll see what I can do to resolve the crash in 32-bit mode on Snow Leopard.

  3. Tom Chappell Tom Chappell

    Does the 32-bit mode solution apply to Affrus, or is Affrus essentially stuck with Leopard? Have put off upgrading for this reason alone, and dreading the day I have to leave Affrus behind.

  4. Just FYI, there’s a wonderful alternative to your XSLT OSAX: /usr/bin/xsltproc called via do shell script. Works like a charm.

  5. Just FYI, there’s a wonderful alternative to your XSLT OSAX: /usr/bin/xsltproc called via do shell script. Works like a charm.

    This is true for cases where you need to translate an XML document on disk. However, XSLT Tools’ extract XML command is unique in it’s ability to extract segments of a larger XML document using XPath. Also, the ability to to define XSLT functions in AppleScript, and thus call AppleScript from your XSL stylesheet, is not possible elsewhere.

Comments are closed.