Re: Scripting support problems
Re: Scripting support problems
- Subject: Re: Scripting support problems
- From: Bill Cheeseman <email@hidden>
- Date: Thu, 30 Sep 2004 05:30:22 -0400
on 2004-09-29 7:41 PM, Doug Knowles at email@hidden wrote:
> I'm still working on redefining my suite as a .sdef, but I have a few
> observations and questions:
>
> - After leaving my project alone for a few days while I was on the road, I
> came back and tried my scripts without making any changes to the project, and
> the script line that wouldn't compile before (set org to root organizer of
> document 1) now compiles and executes correctly. This leads me to ask whether
> the script editor's dictionary is failing to be updated when I build my
> project, or whether the project itself is failing to update when I change the
> dictionary source? Should I be versioning my files, and if so, how?
>
> - An awful lot of documentation, sample code, and web references I'm finding
> still talk about creating .scriptSuite and .scriptTerminology files by hand,
> as opposed to generating them from an .sdef file. I assume the "old"
> technique works to some degree; can someone describe the difference between
> the two approaches?
I used to find that a scriptable application I was developing worked more
reliably after I had moved it to the Applications folder and run it once
from there. I now do that habitually, so I don't know whether it is
required.
It's worth figuring out how to use .sdef files. You've read the relevant man
pages, I assume? Apart from those, it's mostly a matter of trial and error.
Among the advantages of .sdef files are these:
1. In a future version of Mac OS X, Apple indicates that they will be
directly readable at run time so you won't need to mess with Cocoa
.scriptSuite and .scriptTerminology files.
2. Generation of terminology files from .sdef files can be automated in an
Xcode script build phase, making it easier to make and test changes.
3. You can also generate 'aete' resources from .sdef files. Just about any
reasonably complex terminology dictionary will look better to your users,
and in some circumstances work better, if you include both the Cocoa
terminology files and an 'aete' resource in your scriptable application.
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
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.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden