In late June, Apple released Skeleton.sdef, apparently intending it to serve
as the definitive current source for the Standard Suite and the Text Suite
for Cocoa scripting. We are meant to copy and paste the parts of it we
implement in our own scriptable apps.
<http://developer.apple.com/samplecode/ScriptingDefinitions/ScriptingDefinit
ions.html>
However, it contains several errors. At least some of them have been
mentioned here previously, but I am wrapping up a project in which I found a
few others, so I thought it would be useful to put them all in one place.
After allowing a little time for others to comment (either explaining why I
am wrong, or adding more errors), I will file a comprehensive bug.
1. Somewhere recently (the Tiger release notes?), the 'make' command's 'with
data' parameter was said to have been changed to 'with contents'. That's a
good change, but it didn't find its way into Skeleton.sdef.
2. Somewhere recently (the Tiger release notes?), the 'window' class's
'miniaturizable' and 'miniaturized' properties were said to have been
changed to 'minimizable' and 'minimized', but these didn't find their way
into Skeleton.sdef.
3. The 'duplicate' command's 'to' parameter was originally optional, and as
far as I know this has never officially changed (it is marked as optional in
the old-style Cocoa NSCoreSuite.scriptSuite file in Tiger's
Foundation.framework). However, Skeleton.sdef omits the 'optional="yes"'
attribute.
4. The 'duplicate' command originally returned a specifier for the new
object as a return value, and as far as I know this has never officially
changed. However, Skeleton.sdef omits the '<result type="specifier"
description="to the duplicated object."/> element.
5. The 'move' command originally returned a specifier for the
newly-relocated object as a return value, and as far as I know this has
never officially changed. However, Skeleton.sdef omits the '<result
type="specifier" description="to the moved object."/> element.
Nos. 4 and 5 are also wrong in the old-style Cocoa NSCoreSuite.scriptSuite
file. I wonder if the result was omitted there because of limitations in
Cocoa scriptability prior to Tiger? I have had no difficulty implementing
return values in my Tiger app after adding the 'result' element, and they
are of course extremely useful.
All of these errors can be repaired simply by editing the pasted definitions
in one's own custom sdef file.
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
PreFab Software - http://www.prefab.com/scripting.html
The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-implementors mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
