Re: Opening AppleScript *.app files for editing
Re: Opening AppleScript *.app files for editing
- Subject: Re: Opening AppleScript *.app files for editing
- From: Philip Aker <email@hidden>
- Date: Sun, 24 May 2009 22:15:03 -0700
On 2009-05-24, at 20:04:06, Doug McNutt wrote:
At 18:09 -0600 5/24/09, I wrote a question about opening a .app for
editing..
It turns out that I didn't copy the resource fork to the new
directory. CpMac repaired most of the damage.
After opening up the /Users/jim/bin/ directory I was able to edit
and save the APPL but I couldn't just save. I had to do a save-as
and redeclare it to be an APPL. Script Editor doesn't mind just
saving in my space. It's only on Jim's space, while logged in as me
with admin privileges, that I have to do the save-as thing.
But now I'm worried about using my AppleScript on Tiger or Leopard.
I was a bit surprised to find the binary in the resource fork the
way things were on 68k boxes. Is that still the case in more modern
versions of OS neXt? What about Intel machines?
Look at 'man osacompile' on your setup.
If it has a -d option, then scripts can be stored in the data fork and
you should use that format.
You should be able to store them in the resource fork as well and
maintain compatibility with older systems.
Philip Aker
echo email@hidden@nl | tr a-z@. p-za-o.@
Democracy: Two wolves and a sheep voting on lunch.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden