Re: How to "Tell" a varible name (solved??)
Re: How to "Tell" a varible name (solved??)
- Subject: Re: How to "Tell" a varible name (solved??)
- From: Paul Berkowitz <email@hidden>
- Date: Thu, 08 Feb 2001 07:16:22 -0800
On 2/8/01 1:58 AM, "Pier Kuipers" <email@hidden> wrote:
>
>>> The "Raw codes" method looked like it should work, so I tried it,
>
>>> using Smile to get the codes. The problematic source script snippet
>
>
Can anyone tell me how to get the "Raw Code"? I'm intrigued by this
>
way of scripting, since it seems to me that it makes it easier to
>
distribute scripts.
>
Thanks,
>
>
Pier.
You already have Smile, I believe. Use the "tell
" menu item (Edit menu) to
target a SCRIPT window (not text window) to the application concerned and
paste in a whole script or a "balanced" script snippet (full repeat or try
blocks, etc.). Remove any outer tell/end tell application commands. Click
the Check Syntax button. Select the whole script, or part of it, and use the
application button at the bottom, or the edit menu, or press
option-command-C, to "Copy Translate" the selection. Open a fresh script (or
text) window and paste.
You will see all the application's classes, properties (as classes) and
events in raw code. This doesn't work for AppleScript (no-application) terms
or osaxen.
For osaxen use Jon Pugh's technique. Option-drag the osax from Scripting
Additions folder to copy it to your desktop or anywhere outside the System
folder. Then move the original from SA folder to the trash, and empty the
trash. Then recompile a script containing osax commands. You'll see the raw
code. To get the osax working again, just move the copy back to the SA
folder and recompile the script again.
I don't know how to do it for AppleScript terms. Someone?
Paul Berkowitz