Re: Compiling Classic osaxen in OS X
Re: Compiling Classic osaxen in OS X
- Subject: Re: Compiling Classic osaxen in OS X
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 08 Aug 2001 18:44:49 -0700
On 8/8/01 7:34 PM, "Bob.Kalbaugh" <email@hidden> wrote:
>
Bill Fancher sent me the solution. It works. You do the two steps one at a
>
time. First you put the osax commands in a 'using terms from alias pathName'
>
block (pathName being the path to the osax in the OS 9.1 Scripting Additions
>
folder) and compile. That gives you the raw code in chevrons of the osax
>
command. Then you have to REMOVE the 'using terms from' block (to avoid that
>
'scripting component error') and wrap the lines, plus any others needed, in
>
a 'tell application "Classic App" ' block.
Yes! that's the quicker way I was trying to remember. Thank you, Bob. I
forgot you had to remove the 'using terms from' after NOT specifying a
Classic app in the first place. Most peculiar method. I've actually done
this a few times where I knew the raw code, without problem. This particular
time it didn't work, even with uncompiled raw code, because it was a command
requiring a parameter, which I forgot translates into an interpolated
'given' when compiling in raw code. Repeating Bill's method here found it
for me. And of course Chris Espinosa's method also works (even weirder), but
you don't want to leave in the hard-coding to your own osax location when
exporting this either.
What's so odd about both methods is that you have to avoid naming the
application by its real name when compiling the osax terms.
--
Paul Berkowitz