Problems with OO and Applescript

[Ben Bornstein]

Hi Curtis, Wes, Michael,

      Thanks so much for you prompt responses.  I didn't try 
'osacompile', but it's nice to know its there.  Smile 
(http://www.satimage.fr/software/en/softx.html) worked, though I found 
I needed to cut-and-paste the script into a new document; i.e. Smile 
seems to honor and preserve scripts saved in the data fork.  (This 
whole data / resource fork dichotomy is a bit foreign to me, I'm a 
recent Linux convert).

      Although slightly off-topic, is it possible to edit Applescripts 
with Xcode?
When I drag-and-drop a script on Xcode I either get an empty file 
(resource fork, I presume) or a bunch of binary garbage (data fork).

      I'll follow-up on the bug report and event registration feature 
request shortly.

      Thanks again!


Ben


On Mar 3, 2004, at 12:50 PM, Curtis Clifton wrote:

>> Script Editor changed in Panther to place the compiled code for newly 
>> created scripts in the data fork of the script instead of in the 
>> resource fork.  Scripts run from the OO scripts menu only work if the 
>> compiled code is in the resource fork.  There are a few alternatives:
>>
>> - Save your script as text and compile it from the command line using 
>> osacompile.  (Try 'man osacompile' for info.)
>>
>> - Find a script that works in OO.  Copy the script using the Finder 
>> (to preserve the resource fork) and rename it to the name you want 
>> for your script.  Open the copy in Script Editor and paste your code 
>> into the editor.  Since the compiled code is already stored in the 
>> resource fork, Script Editor will put the compiled code for your 
>> script in the resource fork also.
>>
>> - Use a different script editor.  Smile from Satimage has been 
>> recommended to me, but I haven't used it yet. 
>> http://www.satimage.fr/software/en/softx.html