Re: solutions to scripting addition terminology confilicts
Re: solutions to scripting addition terminology confilicts
- Subject: Re: solutions to scripting addition terminology confilicts
- From: "Neal A. Crocker" <email@hidden>
- Date: Fri, 1 Feb 2002 14:51:55 -0800
Date: Tue, 29 Jan 2002 12:02:19 -0800
To: email@hidden
From: Jon Pugh <email@hidden>
Subject: Re: solutions to scripting addition terminology confilicts
At 10:22 PM -0500 1/28/02, email@hidden wrote:
> 1. Put the 'Foobar Addition' in the Scripting Additions folder
> 2. Put the 'Foobar Terminology' anywhere you want.
> 3. To use the handlers in the scripting addition, write,
>
> using terms from application "Foobar Terminology"
> foobar
> end using terms
Now you don't get notified of terminology conflicts?
What conflicts? If the osax which is put in the Scripting Additions
folder contains no aete, it supplies no terminology to conflict with
anything. If all the terminology necessary for compiling against it
is put in some other folder an invoked with the "using terms from"
block, that terminology only has effect inside the block. If all
osaxen are similary factored, as suggested, into separate loadable
code and terminology files, the only global terminology left to
conflict with is Applescript's, which osaxen developers should stay
away from anyway.
Neal.