Painless Software Schedules and OO

[James Lorenzen]

On Mar 15, 2004, at 4:46 PM, Wes Meltzer wrote:

> At 4:39 PM -0600 3/15/04, James Lorenzen wrote:
>
>
>> I tried one of the resource fork v data fork solutions (take a 
>> working script and paste the code into it).
>
> Easier yet: Run osacompile on the script in Terminal. Isn't much of a 
> hassle and doesn't involve some kind of ridiculous hack.
>
> It would be better if somehow, you know, Script Editor got this right 
> on its own, but I'd like to think that the process of compiling a 
> script makes more sense at least than a total kludge.
>
> Wes :wm
> -- 

Well, I cheerfully did the "osacompile", note reading the man page is a 
good thing (tm).  It created the script in the resource fork.  Same 
results.

Let me see....  Consistency, that's a good thing, huh?

James