-
Scripting Additions Updated
After an extremely long gestation in Beta I’ve released 64-Bit Intel compatible versions of the following Scripting Additions:
-
Snow Leopard vs My Scripting Additions, Part 3
In a previous post I released beta builds of Snow Leopard versions of 3 out of 4 of my AppleScript Scripting Additions.
The remaining Scripting Addition, XSLT Tools, has proved to be a difficult problem to solve. XSLT Tools makes heavy use of Carbon APIs that are not available to 64-bit builds on Snow Leopard. However, even the existing 32-bit version crashes on Snow Leopard systems.
Here is a new 32-bit Snow Leopard/Intel only build of XSLT Tools that no longer crashes:
In order to use this version of XSLT Tools, you need to run the AppleScript Script Editor, applets and droplets in 32-bit mode. This is done by modifying these files using the Finder’s Get Info panel and then checking the 32-bit mode checkbox.
-
Snow Leopard vs My Scripting Additions, Part 2
UPDATE: Final versions of these Scripting Additions have been released.
In a previous post I described how my Scripting Additions were incompatible with Snow Leopard (Mac OS X 10.6).
I am developing new versions of XML Tools, Property List Tools and List & record Tools which are 64-bit native and take full advantage of the new capabilities of Snow Leopard (multi-threading). The problem is that my Intel hardware is 32-bit Core Duo based (Original MacBook Pro) so I cannot fully test the 64-bit part. If you have scripts that use these scripting additions on 64-bit Intel hardware running Snow Leopard, please download and test these beta builds and report any problems:
IMPORTANT NOTE: Due to bugs in Mac OS X 10.5 (Leopard), it is not possible to make a Scripting Addition that takes full advantage of Mac OS X 10.6 (Snow Leopard) and also be backward compatible with Mac OS X 10.5. As a result, these builds are Intel only, and should only be used with Mac OS X 10.6.
For those who use my XSLT Tools scripting addition, I’m finding that the underlying XML and XSLT libraries make heavy use of Carbon APIs that are not available on 64-Bit Mac OS X 10.6. As a result, I’m still not sure if I’ll be able to create an upgraded version of this Scripting Addition.
-
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.
-
XML Tools 2.9.2
I have just uploaded a new version of my freeware XML Tools AppleScript Scripting Addition. This new release addresses a regression in the 2.9.1 release that prevented XML Tools from loading correctly on Mac OS X 10.4 (Tiger) systems.
-
XML Tools 2.9.1
I have just uploaded a new version of my freeware XML Tools AppleScript Scripting Addition. This new release addresses a series of issues that have come to light since the 2.9 release in June, 2007.
Changes in this release:
- Resolved a crashing bug that occurred when parsing XML data containing XML namespace declarations on elements other than the root element.
- AppleScript errors signaled from the
XMLParseResultSAX event handler are now reported to the script invoking theparse XMLcommand. Previously, errors signaled from this handler would case the handler to fail silently. - AppleScript errors signaled from SAX event handlers are now reported to the
XMLParseResultSAX event handler via parameters. TheXMLParseResultevent handler is now declared as:on XMLParseResult(errNumber, errMessage). Note that these parameters are optional which allows existing code lacking these parameter declarations to continue working unaltered.
-
XSLT Tools 2.1.2
I’ve just uploaded a new version of my freeware XSLT Tools AppleScript Scripting Addition.
This build addresses a problem that caused errors when non-literal parameters were passed to AppleScript handlers from XSL stylesheets. For example,
<xsl:value-of select="ns1:AppleScriptHandler($stringVar)"/>would fail in the past. -
XSLT Tools 2.1.1
I’ve just uploaded a new version of my XSLT Tools AppleScript scripting addition. This build addresses a problem that was introduced by Mac OS X 10.5 (Leopard). This problem prevented XSLT Tools from correctly parsing XML passed to it as a UTF-16 string.
subscribe via RSS