Re: Compiled Script vs. compiled script
Re: Compiled Script vs. compiled script
- Subject: Re: Compiled Script vs. compiled script
- From: Christopher Nebel <email@hidden>
- Date: Sun, 2 Mar 2003 13:05:41 -0800
On Sunday, March 2, 2003, at 12:39 PM, Rob Jorgensen wrote:
At 11:43 AM -0800 3/2/03, Christopher Nebel wrote:
In Script Editor 2 ... you have "compiled script" and "script
document", but that's a different problem.
However, Paul is incorrect: there is no difference between "Compiled
Script" and "compiled script". The idea that one does resource-fork
and one does data-fork is a myth, which I think got started as a
random guess from someone trying to explain why the heck there were
two items in the first place.
In fact, Script Editor 1.9 saves all new scripts as data-fork;
existing scripts are saved as whatever they were. (I.e., open a
resource-fork script, save it; it's still a resource-fork script.)
Prior to 1.9, all scripts are saved as resource-fork.
Thanks for the clarification Chris. Now, what's the difference between
"compiled script" and "script document" in Script Editor 2? :P
Surrounded by comedians, I tell you. :P
"compiled script" is the same as "compiled script" in Script Editor
1.9. (I.e., nominally a data-fork script, but it'll adapt to existing
files.) "script document" is a bundled script document; it's like the
difference between .rtf and .rtfd in TextEdit. We'll come up with
something more comprehensible for 2.0 final.
--Chris Nebel
AppleScript Engineering
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.