Re: OS X replacement for Script Scheduler
Re: OS X replacement for Script Scheduler
- Subject: Re: OS X replacement for Script Scheduler
- From: "Donald S. Hall" <email@hidden>
- Date: Thu, 09 May 2002 15:10:06 -0600
>
From: garbanzito <email@hidden>
>
Date: Wed, 8 May 2002 22:21:22 -0600
>
To: "Donald S. Hall" <email@hidden>, <email@hidden>, AppleScript
>
Mailing List <email@hidden>
>
Subject: Re: OS X replacement for Script Scheduler
>
>
at 2002 05 08, 18:10 -0600, they whom i call Donald S. Hall wrote:
>
> Script Timer has several advantages over cron when it comes to
>
> scheduling the running of AppleScript scripts, largely because a) cron is a
>
> general purpose Unix utility, and
>
>
could you elaborate on how that's an advantage?
Mainly because Script Timer is intended for use with AppleScript scripts
(although it can run any program or open any file for which you have
sufficient privileges), while cron is designed to schedule Unix processes.
Two of the specific advantages I broke out (easy parameter passing, logging
of script results). There are more listed on the Script Timer FAQ page,
which you can get to by going to the Apps & More web site below and clicking
on the Shareware and Freeware button, then on the Script Timer link. The
relevant FAQ is #6.
>
>
> b) most scripts must be saved as
>
> applications to be run by cron.
>
>
just curious, do you say this because osascript doesn't
>
allow scripts with user interaction?
>
This was discussed in the AppleScript User's mailing list within the last 6
months or so. Here is part of what Chris Nebel of AS Engineering wrote:
>
>> You're seeing a security "feature." It has to do with Mach messages,
>
>> which form the guts of Apple Events on Mac OS X. For security reasons,
>
>> processes in Mach are segregated into "process groups", and a process in
>
>> one group is not allowed to send messages to a process in a different
>
>> group. Because cron gets launched at boot time, it's in root's process
>
>> group, while every application launched by your login (including the
>
>> Finder) is in your process group. Therefore, a script run by cron can't
>
>> talk to any application that you launched.
I believe this means that any script with a tell statement must be made into
a Script Application to be run with cron. This adds at least 52 K to a very
short script that would otherwise be a few thousand bytes.
>
> Also, you can pass parameters to your
>
> scripts with Script Timer, and Script Timer can accept data back from the
>
> script for logging in its own log file.
>
>
now that's an advantage, otherwise you have to do
>
contortions to pass parameters (text only) via
>
osascript.
Script Timer comes with a Reminder script that puts up a dialog with a
message. To use it you just schedule it like this:
Reminder(Time for lunch!) weekdays 11:55 am
>
>
--
>
steve harley email@hidden
>
HTH,
Don
--
Donald S. Hall, Ph.D.
Apps & More Software Design, Inc.
http://www.theboss.net/appsmore
email@hidden
_______________________________________________
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.