Re: AppleScript Timed Events
Re: AppleScript Timed Events
- Subject: Re: AppleScript Timed Events
- From: John Delacour <email@hidden>
- Date: Wed, 18 Jun 2003 10:13:16 +0100
- Mac-eudora-version: 6.0a21
At 12:21 am -0600 18/6/03, Donald Hall wrote:
I have been reading this thread with interest. If you want to keep
things in AS, then John Delacour's little script looks good. If you
want to schedule scripts to run (or applications for that matter),
I invite you to look at an application I publish called "Script
Timer".
This looks very nice, though I haven't had time to use it yet.
Sincere thanks to Deivy for the very clear explanation of how to use
at. But.....
At 10:11 am -0400 17/6/03, Deivy Petrescu wrote:
Simone, forget what everybody else writes and use "at".
I think this is another example of the gulf that exists between the
Mac way of thinking and the thinking of UNIX people who use (and
quite like) the new Mac. Many of these (and I'm not including Deivy)
consider Applescript and Apple events as toys for the arty-farty
byte-ignorant sandal-wearers that make up the Mac community and are
unable to see how much is to be gained from learning how to use them
and especially using them to provide a smooth and fast interface to
the underlying system and the shell. Some of these will never be
convinced and will continue to use OS X as a sort of glorified UNIX.
Donald's app looks great. Things like this and iKey (and formerly
the sadly missed OneClick) provide the user interface for Apple
Events that Apple has always failed to provide, but it is possible to
produce a thoroughly good script scheduling package using only
Applescript that is easy to manage (a simple text file) and more
flexible even than Script Timer -- let's say something that will
accurately confirm your killer bid on eBay seven seconds before the
hammer falls.
<<at>> is clumsy, cannot run a compiled script, and has a minimum
interval of a minute. I reckon also that at least half the people
who try to follow Deivy's instructions, clear though they are, will
be tearing their hair out after twenty minutes trying to work out
what they're doing wrong.
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. A stay open
applet runs compiled scripts. That is to say it takes no time (cf.
osascript -yuk) compiling code and it takes no time and creates no
disturbance launching applets -- it runs the scheduled task silently
(if possible) on the second.
When I have a moment, I'll upload a full working bundle of what I'm
talking about.
JD
_______________________________________________
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.