Re: AppleScript Timed Events
Re: AppleScript Timed Events
- Subject: Re: AppleScript Timed Events
- From: Nigel Smith <email@hidden>
- Date: Wed, 18 Jun 2003 11:20:59 +0100
On 18/6/03 10:13, "John Delacour" <email@hidden> wrote:
>
<<at>> is clumsy, cannot run a compiled script, and has a minimum
>
interval of a minute.
From the osascript man page:
"osascript executes the given script file, or standard input if
none is given. Scripts may be plain text or compiled scripts."
at's big advantage over an AppleScript package is that, as Deivy pointed
out, you don't have to be logged in to the machine for it to work. So, for
example, I can use it to schedule a system software update and restart on a
server at 3am, rather than disrupt the lab during work hours or set my alarm
clock and log in from home.
>
My example of how to do things with a stay-open applet was merely an
>
example. It would not take long to write a little package that would
>
be bullet-proof, easy to use and infinitely extensible.
<snip>
>
When I have a moment, I'll upload a full working bundle of what I'm
>
talking about.
Looking forward to it already. Just out of interest -- what do you plan to
do if a user logs in, and therefore starts the scheduler, 10 minutes after a
scheduled job should have run? Will you ignore all past jobs, or keep a log
of completed jobs so you can run those which should have happened but
didn't? Will there be a switch so the user can choose which jobs should be
run after their scheduled time? Dialogs which ask?
As you can probably tell, I thought about creating a similar package,
started wondering about the above issues, and promptly put my head back
under the duvet...
Later,
Nigel
_______________________________________________
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.