Amiga Format CD 13

home *** CD-ROM | disk | FTP | other *** search

/ Amiga Format CD 13 / amigaformatcd13.iso / -seriously_amiga- / shareware / misc / ezcron / doc / ezcron.guide (.txt) next >

Wrap

Amigaguide Document | 1997-03-06 | 36KB | 669 lines

@database EZCronGuideFile @master EZCron.guide @$VER: EZCron v2.00 Guidefile @WORDWRAP @node "Main" "No title" @{b}EZCRON v2.00@{ub} @{fg shine}February 1997@{fg text} @{" " link "Author" 0} Legal Stuff and Contacting the Author @{" " link "Introduction" 0} Introduction @{" " link "Requirments" 0} System Requirments @{" " link "Up_and_Running" 0} Running EZCron & EZCrond @{" " link "Buttons" 0} Buttons Reference @{" " link "Tutorials" 0} Tutorials @{" " link "Rexx_Scripts" 0} Overview of included Rexx scripts @{" " link "TroubleShooting" 0} Troubleshooting @{" " link "cronconfig" 0} The NEW cron.config file, an overview. @{" " link "History" 0} Program History @{i}EZCron is 1995-1997 Jim Hines All Rights Reserved @endnode @node "Introduction" "Introduction" @{b}@{i}@{fg shine}EZCron Introduction@{ub}@{ui}@{fg text} This project was started mainly because I had a need to run lightwave between newscasts (I work for a television station) and do automated rendering whenever I wasn't present. The program has grown from a simple rexx script to a full fledged GUI oriented program that is easy to use, and doesn't require a knowledge of UN*X to make it work. EZCron actually consists of two programs. The first is the EZCrond (daemon) which runs as a background process transparently to the user. It's very small and pretty fast. EZCrond will sleep between every minute,only awaking to check if there are any events that need be executed. Its CPU usage is minimal! The second program, EZCron is the user-interface (formally EZCronGUI). This is the Event Manager and allows you to easily add and edit your events. It will also allow you to start and stop EZCrond. @endnode @node "Requirments" "Requirments" @{b}@{i}@{fg shine}SYSTEM REQUIRMENTS@{ub}@{ui}@{fg text} EZCron should run on any Amiga with Workbench/Kickstart 2.04 or better with 512k of ram. This programs/librarys are required to make various parts of the EZCron programs work. - @{b}RexxMast@{ub} MUST be running - @{b}ARexxPort.library@{ub} by Andy Cook (included) - @{b}RexxReqTools.library @{ub}37.71 or later (included) - @{b}Varexx@{ub} by Andy Cook (included) @endnode @node "Up_and_Running" "Getting up and running" @{b}@{i}@{fg shine}Getting Up and Running@{ub}@{ui}@{fg text} @{b}INSTALLATION@{ub} ********IMPORTANT******** As of version 2.00 of EZCron, a lot has changed. Please DELETE the contents of your old EZCron directory before installing this one. You can also copy the old one into another directory if you like. ******************** To run EZCron, you first need to install it. This can be done simply by double clicking the EZCron-Install icon. Or, if you're like me and want to install it manually, see @{"MANUAL INSTALLATION" link "ManualInstal" 0}. The installation script will add a startup command to your s:user-startup sequence. It will also add an assign for EZCron. You must reboot for the assign to take effect. After you reboot, EZCrond should be running. There are two ways to check. The easiest is to simply double-click on the EZCron icon in the EZCron: directory, and look at the EZCron Status gadget. It will either say "Active", or "Inactive." @endnode @node "ManualInstal" "Manual Installation" @{b}@{i}@{fg shine}MANUAL INSTALLATION@{ub}@{ui}@{fg text} - Create a directory called EZCron. - Copy the EZCrond program to your EZCron directory. - Copy the EZCron program and EZCron.info to your EZCron directory. - Copy the contents of the libs directory to your libs: directory. - Copy the contents of the s directory to your s: directory (s: is located in sys:s and is assigned by the kickstart ROM). - Copy rexxc/varexx and vxc to your sys:rexxc directory. @{i} The following directories @{b} MUST @{ub} be present in your EZCron directory.@{ui} - Copy the prefs directory to your EZCron directory. - Copy the rexx directory to your EZCron directory. @{i}The following @{b} MUST @{ub} be added to your s:user-startup file:@{ui} ;Added for EZCron assign EZCron: [yourdevice]:EZCron run >nil: rx >nil EZCron:EZCronD Start ;End EZCron If you are running OS3.1 this assign can be like this: ;Added for EZCron assign EZCron: [yourdevice]:EZCron run <>nil: rx EZCron:EZCronD Start ;End EZCron That should do it. Just reboot and run EZCron when you want to add, edit or remove events. @endnode @node "Buttons" "Buttons" @{b}@{i}@{fg fill}LISTING OF BUTTONS AND FUNCTIONS@{ub}@{ui}@{fg text} @{"E" link "E"} Event @{"A" link "A"} Arguments @{"S" link "S"} Sfx @{"D" link "D"} Date @{"DateRange" link "daterange" 0} Date Range @{"T" link "T"} Time @{"Time Range" link "TimeRange"} Time Range @{"Add" link "Add"} Add Event @{"Test" link "Test"} Test Event @{"Del" link "Del"} Delete Event @{"Mod" link "Mod"} Modify Event @{"TEdit" link "TEdit"} Edit with text editor @{"New" link "New"} New Config File @{"Purge" link "Purge"} Purge old events @{"E/D" link "E/D"} Enable/Disable Event @{"MkDef" link "MkDef"} Make Default Event @{"Refresh" link "Refresh"} Refresh List/Status @{"Clock" link "Clock"} Run a clock @{"Prefs" link "Prefs"} Set/Change Preferences @{"Control" link "Control"} Set/Change Preferences @endnode @NODE E @{fg shine} - E (Create a new event)@{fg text} This is the gadget you use to create a brand new event. This will bring up a requester that asks you what type of event you would like. There are two types: @{i}Program Event: @{ui} This is the event type you would select for running external events. An external event could be an executable program, a rexx script or a dos script etc. If you select the program event, it will bring up a file requester for you to choose the program you wish to execute. Make sure a full path is given, or the program may not execute properly! When a program is selected, the CURRENT time and date are filled in the time and date fields. You will need to change these to reflect the time and date you wish your program to run. Also, be sure to TEST the event to make sure it works properly before you depend on the EZCrond (daemon) to start it automatically. @{i}Reminder Event: @{ui} When you select REMINDER, it will bring up a string requester that allows you to enter a text string. Once set, this will also automatically set the Event field to @{b}TEXTREMINDER@{ub}. This must remain @{b}TEXTREMINDER@{ub} in order for the program to understand its task. When @{b}TEXTREMINDER@{ub} is selected, the CURRENT time and date are filled in the time and date fields. You will need to change these to reflect the time and date you wish your text reminder to be displayed. @{b} NOTE: You must click the ADD button after creating the event.@{ub} @endnode @node T @{fg shine}- T (Time)@{fg text} ** PLEASE NOTE THAT THIS WORKS ON A 24 HOUR CLOCK ** This gadget brings up a window containing a list of gadgets which allow you to select the time format you wish. The options follow with their explainations: Once - Run the even only once. ie: 13:22 Minute - Run the event every minute of every hour Five Min - Run the event every five minutes of every hour. Ten Min - Run the event every ten minutes of every hour. Quarter - Run the event at 00, 15, 30, & 45 minutes of every hour. Thirty - Run the event at 00, and 30 minutes of every hour. Hourly - Run the event every hour on the hour. *Special - Run the event via wildcards. The default is set for every hour at a specified minute. The hour place will be replaced with the pounds sign. ie: ##:33 would run the event every hour at 33 minutes after the hour. Also, you may manually change the minute field to the wildcard as well. ie: 15:## would run the event every minute from 15:00 to 15:59. A third option is to set it for ##:##. This would run the event every minute of every hour. This would be the exact same as selecting 'Minute' in the time field. @endnode @node timerange @{fg shine} - Start Time/End Time @{fg text} These gadgets represent a time range you may want an event to execute within. If you wish your event to run from noon to 3pm you would enter 12:00 in the Start Time gadget and a 15:00 in the End Hr. gadget. Please note that events that run from PM to AM MUST be set up as two seperate events. EZCrond (daeman) works on a 24 hour clock internally. If, for example you wish your event(s) to run from 11pm to 3am you would have to set up your first event to run from 23:00 to 24:00 and then your second event to run from 00:00 to 03:00. I am VERY aware that there is not really a 24 in the 24 hour format, but it has to be done this way in order to work properly. In other words, Midnight has to ALWAYS be entered as 24 when used as an end time and 00 when used as a start time. Of course, you could enter 23:59 as the end time on one event and 00:00 as the start on another. @{b}Wildcard Support@{ub} Currently, EZCrond and EZCron does not support wildcards within date ranges. @endnode @node D @{fg shine}- D (Date)@{fg text} This gadget brings up a window containing a list of gadgets which allow you to select the date format you wish. The options follow with their explainations: Once - Run an even only once. ie: 13:22 Daily - Run an event every day. Monthly - Run an event one day a month. The actual field would be 'Monthly-00' where '00' is the date. ie. Monthly-14 would execute the event every month on the 14th. Sun-Sat - Run an event on the given day of the week. Weekdays - Run an event on Saturdays and Sundays only Weekends - Run the event Mon-Fri only. EveryNNDD - This is a strange one. This option will allow you to run events one given days in weeks of the months. ie: 'Every_3_Fri' would run the event every third friday of every month. 'Every_1_Mon' would run the event every first Monday of a month. Range - This option will allow you run events within a range of dates. *Special - This is where it gets fun. This allows you to use wildcards for your event dates. The first field of wildcards represents the month. The next field of wildcards represents the day. The last field of wildcards represents the year. When selected, the date window will contain '##/##/##'. This means that the month, day and year are all set for 'on' and the event would run every day of every month of every year. If you wanted the event to execute every day during March of 1997, if would look like this: '03/##/97'. If you wanted the event to execute every month on the 12th in 1997, you would change it to this: '##/12/97'. This would be the same as if you had used 'Monthly-12'. @{b}@{i}* - Designates new additions or changes since previous release. @{ub}@{ui} @endnode @node daterange -@{fg shine} Date Range @{fg text} The date range feature allows you to set a range of dates for a given event. If, for instance, you wish to run an event every day from January 1, 1997 to March 14, 1997, you would enter 01/01/97 as the start date and 03/14/97 as the end date. @{b}Wildcard Support@{ub} The date range also supports wildcards. This drastically opens up the possibilities of date ranging. By using wildcards, one could set up a single event to execute at given times throughout a month, week or year. Keep in mind that a range will override any date setting you may have. This is difficult to explain so I will use examples to try and make it easier to understand. Date: ##/##/97 or Daily Startdate: ##/14/97 This would run an event every month of 1997 on the Enddate: ##/18/97 14th through the 18th only. Date: ##/##/97 or Daily Startdate: 01/##/97 This would run an event every day thoughout January Enddate: 02/##/97 and Feburary of 1997 only. Date: Every_3_Fri Startdate: 01/14/97 This would run an event every third Friday from January Enddate: 06/##/97 14th through the last day of June. Date: Saturday Startdate: 01/14/97 This would run an event every Saturday from January 14th Enddate: 05/##/97 through the last day of May. @endnode @node ED -@{fg shine} E/D (Enable/Disable Event)@{fg text} (NEW v1.75+) This switch is the Enable/Disable gadget. It does just what it says, it enables and disables events. This will add a '!' charactor to the beginning of the event name. The Daemon will not execute events marked in this manner. To use this feature, simply select the event you wish to enable/disable and then click the E/D gadget. A '!' charactor will be added or removed from the event field. @{b}NOTE: @{ub}Events may STILL be tested when disabled. @endnode @node mkdef -@{fg shine} MkDef (Make Default Event)@{fg text} When EZCron makes a new s:cron.config file, it must always create one event within the new file (EZCrond (daemon) would simply exit if no events existed). EZCron will create a default event of your choice simply by clicking on an event in the listview window, or by creating an event, then clicking the @{b}MkDef @{ub}gadget. You could set the default event to be dated sometime in the past so that the default event never actually runs. @{fg fill}Note: @{fg text}If you do make the default event a past date, beware that the @{b}Purge@{ub} gadget WILL delete it. @endnode @node A -@{fg shine} A (Event Arguments)@{fg text} This brings up a ReqTools file requester for adding program file arguments. Be sure that your paths are complete. If the argument is not a file, you may type the argument in manually in the text field. @endnode @node S -@{fg shine} S (Sound Effect/Sample)@{fg text} This gadget brings up a ReqTools file requester for adding an optional sound effect to be played with a given event. Once again, make sure a full path in included here. The Sample Player Prefs must have some sort of audio player set like playsound, Play16, etc. @endnode @node ADD - @{fg shine}Add (Add New Event/Copy Event)@{fg text} This gadget allows you to add your new event or copy an existing one. To create a new event, you must add all of your parameters FIRST then click the @{b}ADD @{ub}gadget to add it to the list. If coping an existing event, select the event, then click the ADD button. This will copy the selected event to a new one at the bottom of the list. @endnode @node DEL - @{fg shine}Del (Delete Event)@{fg text} Deletes the selected event from the list. There is no safty net here, If you accidently click on the DEL button, the event is gone for good. @endnode @node MOD - @{fg shine}Mod (Modify Event)@{fg text} This will modify the current selected event. First select the event you wish to modify. Make the necessary changes. Click the @{b}Mod@{ub} gadget. @endnode @node PURGE - @{fg shine}Purge (Purge Event List)@{fg text} This gadget will delete old, one time events. It will not delete any events that are still active. ie: events containing the fields Daily or Monthly-xx would not be deleted. It will also delete events that had a date range set on them if the range has expired. @endnode @node NEW -@{fg shine} New (New Config) @{fg text} When clicking this gadget, @{b}EZCron @{ub}will create a new s:cron.config file with a 'dummy' event contained in it. There MUST be at least one event in the config file for the daemon to function (This default event can be set using the AddDef gadget). This event may be a date already passed if you don't wish to be bothered with an active event. This gadget will copy the current config file to s:cron.config.old and create a new one in its place. If you happen to do this by accident, just delete the newly created config file and rename cron.config.old back to cron.config. @endnode @node TEDIT - @{fg shine}TEdit (Call Text Editor)@{fg text} This will call a text editor of your choice (defaults to c:ed) and loads the s:cron.config file into it for manual editing of the cron.config file. You may select an editor of your choice in the prefs settings. @{b}NOTE: ADVANCED USERS@{ub} @endnode @node TEST - @{fg shine}Test (Test Event)@{fg text} This will test the selected event to make sure everything works just fine before you 'trust' it to work on its own. @endnode @node CONTROL - @{fg shine}Control (EZCronD Control)@{fg text} This manually starts and stops the @{b}EZCrond@{ub} (daemon). It simply toggles it on or off. Just remember to start it if events are due to take place. If you used the installer, EZCrond will be started from your startup-sequence automatically. @endnode @node REFRESH - @{fg shine}Refresh @{fg text} This simply refreshes the events listing and the Daemon control status. You may need this if you edit the cron.config file with a text editor that seperates itself from the parent process, for example. @endnode @node CLOCK - @{fg shine}Clock@{fg text} This gadget will pop open a small AmigaDos digital clock. @ENDNODE @node PREFS - @{fg shine}Prefs @{fg text} This gadget takes you to the prefs window where you may set prefs for an audio player and for an optional text editor. @{b}PREFS WINDOW @{ub} - @{fg shine}Choose Text Editor @{fg text} This will choose a text editor and saves its settings. For use with the @{b}TEdit@{ub} gadget. - @{fg shine}Choose Sample Player @{fg text} For adding a sample player to the prefs file. This must be set if you wish to use sound effects with events. - @{fg shine}Set Test Console @{fg text} When testing an event, by default, a con: window will pop up for debugging purposes. This prefs setting decides the attributes and redirection values of the tested event. This could be changed to prt: if desired and the results would be printed. Also, if you wish for no output whatsoever, you can replace this with an empty string. @endnode @node Tutorials Tutorials @{b}TUTORIALS@{ub} A few tutorials are given below to help you understand how to edit and add events. @{b}ADDING A NEW PROGRAM EVENT:@{ub} Click the 'E' button at the top left. A Requester will pop up asking if want a Program or Reminder event. Click on PROGRAM. A file requester will then pop up. Find the program you wish to run and click ok. The program, current date and current time should appear in their respective fields. If this event is one that you only wish to run once, click in the date gadget and change the date to whatever date you want (remember, the format is mm/dd/yy). Otherwise, click on the 'D' button and select and alternate selection. Next, edit the time field to whatever time you desire, or use the 'T' button to select and alternate selection. Click the 'ADD' button. The new event should appear in the listing. @{b}ADDING A NEW REMINDER EVENT:@{ub} Click the 'E' button at the top left. A Requester will pop up asking if want a Program or Reminder event. Click on REMINDER. A string requester will then pop up. Type in the text you want displayed and click ok. The reminder string, current date and current time should appear in their respective fields. Also, the top event field should have displayed "TEXTREMINDER" If this event is one that you only wish to run once, click in the date gadget and change the date to whatever date you want (remember, the format is mm/dd/yy). Otherwise, click on the 'D' button and select and alternate selection. Next, edit the time field to whatever time you desire, or use the 'T' button to select and alternate selection. Click the 'ADD' button. The new event should appear in the listing as TEXTREMINDER. @{b}COPY AN EVENT:@{ub} Click on the event you wish to copy. Click the 'ADD' button. The newly copied event should now appear at the bottom of the event list. @{b}MODIFY AN EVENT:@{ub} Click on the event you wish to modify. Make the necessary modifications. Click the 'MOD' button. The changes should now be applied. @{b}DELETE AN EVENT:@{ub} Click on the event you wish to delete. Click the 'DEL' button. @{b}CREATE A DEFAULT EVENT:@{ub} Click on the event you wish to become the default event. Click on the MkDef button. Now, whenever you create a new config file, this event will be the first one created. @{b}CREATE A NEW CONFIG FILE (s:cron.config)@{ub} Click the 'NEW' button. If you already have a config file, it will ask if you want to overwrite it. Select 'YES'. You will now have a new config file with the default event in it (See CREATE A DEFAULT EVENT). @endnode @node "Author" "Author" @{b}@{i}@{fg shine}EZCron is emailware@{ub}@{ui}@{fg text} EZCron is free. If you like it and use it, I would like to hear from you. Or if you have any suggestions for improvements and new features, I like to hear them. Also, of course, if you find any bugs, I would like to know where they are. My EMail address is: @{i}hines_j@iolinc.net@{ui} or @{i}wdtv@wdtv.com@{ui} Also, visit my Internet Home Page for the latest version of EZCron and for other interesting stuff. http://www.iolinc.net/~hines_j Also, If you are a Star Trek fan, check out the demo of @{b}Trek-The Guide@{ub}. It is a full featured database with pics, sfx and synopsis for each episode with full cross references and misc facts. It is available on Aminet. @{i}Thanks must go to the following people:@{ui} Gene Heskett (For his huge help in figuring out some of these algorithms. . .and for beta testing) Mike Herschede (Another Great Beta Tester) Karl Swisher (For some pretty good ideas) Andy Cook (Author of VArexx for which the GUI wouldn't have been possible) @{b}LEGAL STUFF@{ub} * EZCron & EZCrond 1994-1997 Jim Hines * rexxreqtools.library 1992-1994 Rafael D'Halleweyn * reqtools.library 1992-1994 Nico Francois * VArexx and RexxPort.library 1995-96 Andy Cook @endnode @node "TroubleShooting" "Troubleshooting" @{b}@{i}@{fg shine}TROUBLESHOOTING@{ub}@{ui}@{fg text} @{b} EZCROND WILL NOT RUN ON STARTUP:@{ub} Make sure that the line '@{b}run >nil: rx >nil: ezcron:ezcrond start@{ub}' is in your s:user-startup sequence. Make sure you have a valid s:cron.config file. It will not run without it! A valid cron.config file should contain at least 1 event in the following format: command,args,time,date,startdate,enddate,TimeRangeStart,TimeRangeStop,SFX,ReminderString EXAMPLES: rx,EZCron:rexx/TalkingClock.rexx,hourly,daily,-,-,--,--,-,- TEXTREMINDER,-,22:00,range,01/01/97,12/31/97,--,--,-,Remember to email the author. @{b}EZCRON WILL NOT RUN AT ALL:@{ub} Make sure all the included librarys are installed in Libs:. Make sure that sys:rexxc is in your path. I have found some systems that don't seem to carry their path over to shell processes too well. Try running it from a shell. Just type '@{b}rx ezcron:ezcron@{ub}' The Shell is actually the best method of trouble-shooting since any EZCron errors will be reported to the shell it was run from. If run from WorkBench, all error messages are suppressed. @{b}EZCROND (DAEMON) WILL NOT RUN AT ALL:@{ub} @{b}NOTE:@{ub} EZCrond can also be started from a shell. Just cd to EZCron: then type @{b}run <>nil: rx EZCrond start@{ub}. Any errors should be reported to the shell it was started from. If none of these solutions work, please contact me and describe the problem. My email address is @{i}hines_j@iolinc.net@{ui}. Make sure you have ARexx installed and running. @endnode @node "Rexx_Scripts" "ARexx Scripts" @{b}@{i}Included ARexx Scripts (and how to use them)@{ub}@{ui} There are a few useful ARexx scripts included that you may find useful. You can find them in the the EZCron/rexx directory. I will list them here and briefly descibe what they do and how to utilize them. @{b}AutoGetMail@{ub}: This simple script utilizes both AmiTCP v4.+ and Thor. All it does is start your AmiTCP/bin/startnet script and gets online...then it runs Thor:bin/gettcp and gets your mail and any newsgroups you may be subscribed to. The only setting that is adjustable, and you must adjust this, is the ThorMailBox variable at the top of the script. Just change this to reflect YOUR Thor mailbox. @{b}LWave_EZCron.rexx@{ub}: This script will control Lightwave 3.5+ and start rendering a given project when executed. It is even smart enought to figure out which frame to start on if there are previously rendered frames in the directory. There are variables that need to be set at the top of the script and they are pretty much self explainatory. @{b}Reminder.rexx@{ub}: This script is used internally by EZCron. It is used to control any textreminders you may have set in EZCronGUI. There are no user varibles to set and this script should be left as is. @{b}TalkingClock.rexx@{ub}: This script does exactly what you think....its a talking clock. First, you MUST have speak: mounted. If you are not familier with Speak:, see you AmigaDos manuals. Also, Speak: is not included with with AmigaOS starting with v2.1. @endnode @node "cronconfig" "Cron.config: An Overview" @{b}Cron.config: An Overview@{ub} The cron.config has changed considerably in the past few versions. Old config files ARE NOT COMPATABLE with this new format. You may use this information to modify your existing config file, or just create a new one with EZCron (recommended). *** FOR THOSE YOU WOULD RATHER MAKE THE CONFIG USING A TEXT EDITOR *** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~cut here~~~~~~~~~~~~~~~~~~~~~~~~~~ ; This is the cron.config file. The semi-colon is a comment marker. ; You may use this to remove commands or make comments. You may also ; comment (disable) out events by using the '!' charactor at the head ; of the line. This will allow you to view and modify events that don't ; actually execute. ; The structure of the file is as follows and each field is seperated by a comma: ; ----------------------------------------------------------------------- ; 1st entry: The path & program you wish to run ; 2nd entry: The program arguments ; 3rd entry: The time to execute. This may also be set to 'Minute' and 'Hourly' ; 4th entry: The Date to execute. This may also be set to 'Daily', a day of the ; week such as 'Wednesday', 'Monthy-00' or 'Range'. The Montly must ; have the hyphen and a two digit number in the same format as written ; below. ; 5th entry: The start date. ; 6th entry: The end date. ; 7th entry: Time Range start time. ; 8th entry: Time Range end time. ; 9th entry: The Sound FX File to run with the event ; 10th entry: If event is a textreminder, this field will contain the text. ; ----------------------------------------------------------------------- ; EXAMPLES ; ======== TEXTREMINDER,-,22:00,range,01/01/97,12/31/97,--,--,-,Remember to email the author. !TEXTREMINDER,-,23:14,every_4_fri,-,-,--,--,-,This is the 4th friday event ezcron:rexx/TalkingClock.rexx,-,hourly,daily,-,-,--,--,-,- !Inet:InetScripts/AutoGetMail,-,15:00,daily,-,-,--,--,-,- c:execute,amitcp:Start_AmiTCP,12:00,weekdays,-,-,--,--,-,- System2.1:WBStartup/LineMan,-,hourly,daily,-,-,02:00,22:00,Data:SoundSamples/Sandro_3_4_5.8svx,- c:play16,Data:SoundSamples/DoubleBeep,quarterly,daily,-,-,--,--,-,- @endnode @node History @{b}EZCron@{ub} ** EZCron is The Graphic User Interface Prefs for EZCrond, 1994-1997 Jim Hines. ** 12-13-95 Added Speech Function to test subrtn. ** 12-22-95 Added Purge Function. ** 12-24-95 Added multi-windowing on prefs window ** 12-31-95 Added multi-windowing cyclegads on time and date fields ** Changed the main gui interface window and moved the new config ** button to the edit screen. Removed the Quik Add button altogether. ** 01-05-96 Added Weekdays, Weekends and Quarterly support. ** Added full online help subroutine. ** 01-07-96 Added Default Event Variable Handling. Opens prefs file at beginning ** and rereads it with the 'addefault' command. ** added online help for def event button. ** 08-25-96 Changes the cron.config file to reside in envarc: and RAM:ENV ** Great idea Paul. ;) ** 09-02-96 Moved the active config file to ram:t as the env: was causing HD ** activity with such programs as HDEnv. The cron.config is now BACK ** in s: but copied to t: ** 09-09-96 Started work on the range stuffs ** 09-10-96 Hourly time range routine added. ** 09-11-96 Fixed a few bugs and tightened the code up a bit. ** 09-18-96 Added the every 5 minutes time field. ** 10-10-96 Fixed a nasty clock bug in the I/O button which caused the GUI to exit. ** This occured after being in the event editor, then exiting to the ** control panel and then quiting the daemon. ** 01-07-97 Added the ENABLE/DISABLE EVENT function ** 01-08-97 Rewrote the GUI section entirely. Now smaller and faster since the ** main loop is much much smaller!!! ** 01-09-97 You can now test disabled events. Line 210 ** 01-14-97 More speed rewrites: seperated the waitforpkt() from the eventparse() ** shortening the main loop even more. ** Added Ten_Min and Thirty_Min to the time fields. ** 01-18-97 Fixed a nasty bug; If you tested a disabled event, then enabled ** the event, the argument 1 field would get copied to the other 3. ** TOOK OUT THE DELAYS() ** Added a check for an empty cron.config file. Used to cause a startup error. ** 01-20-97 Fixed a bug in the testevent(). It was lacking the double quotes which was ** causing problems. ** 01-25-97 Reworked the event gadget. It now will ask what type of event you want. ** 01-27-97 Fixed a bug in Purge:. ** Fixed a bug in Prefs:. ** 01-29-97 Started on the Date Range function. ** 01-30-97 DateRange function implemented, but still a little buggy. ** 02-01-97 Now supports unlimited arguments. ** Now using commas between fields. Old config is no longer compatable ** as of v1.84e ** 02-04-97 Eliminated the online help system. With the new GUI, its much easier ** to understand and it was felt that it was no longer needed. ** 02-06-97 ReqTools requesters will now open under the mouse pointer. ** 02-07-97 Rewrote the update() routine. It will no longer put modified events ** at the bottom of the list. ** 02-07-97 Reduced the deleteevent() and adddefault code majorly. ** Added a comma after the last field. ** Cleaned up extra, unneeded copy to t: routines. ** 02-08-97 Blank date range double dashes (--). Now it's a single dash (-). ** 02-09-97 Added the shour to the time menu. ** 02-09-97 added the hour wildcard '##'. ie: '##:15'. AF (advanced feature #1) ** 02-10-97 Renamed EZCronGUI to EZCron ** 02-12-97 Renamed the MAINWINPORT to EZCRON_PREFS. ** EZCrond can now auto update the daemon status window. ** 02/14/97 Renamed EZCron to EZCrond and EZCronGUI to EZCron. ** Sorry for the confusion, but they really needed renaming. ** The ARexx ports were also renamed to EZCROND and EZCRONPREFS. ** 02/16/96 Added a new prefs option: Test Routine Redirection. ** Changed cprefs to defev.prefs. @{b}EZCronD @{ub} /* $VER: EZCrond by Jim Hines v1.85 1995-1997 All Rights Reserved ** 10-23-95 Added requester to verify making a NEW cron.config file. See newrtn: ** 10-25-95 Fixed Bug in the above and added renaming of the old config file. See newrtn: ** renamed from ACron to EZCron. GUI started on this date too. ** 11-30-95 added the text string reminder support and the sfx functions ** 12-05-95 Fixed case sensitivity problem with weekly, monthly & Daily routines ** 12-13-95 Added Speech Function ** 01-04-96 Added Weekdays, Weekend and Quarterly support functions ** 01-05-96 Fixed a bug in the Weekdays routine. ** 01-11-96 Cleaned up the code a bit ** 01-17-96 Added a new routine. ie every_3_wed ** 08-25-96 Moved the cron.config file to envarc: / RAM:ENV ** Good idea Paul. ;) ** 09-02-96 Moved the active config file to ram:t as the env: was causing HD ** activity with such programs as HDEnv ** 09-10-96 Hourly time range routine added. ** 09-11-96 Fixed a nasty bug in time range and majorly rearranged the timer code. ** Version bumped to 1.70. Thanks Gene! ** Finally renamed the rexx port from ACron_Rexx to EZCron_Rexx. ** 09-18-96 Added the every 'Five_Min' time field. ** 10-03-96 Actually made it work (What took me so long?) ** 01-07-97 The daemon now also ignores the '!' charactor as a comment. This is used ** by EzCronGUI to disable events without removing them from the list. ** 01-14-97 Now supports Ten_Min and Thirty_Min events. ** 01-20-97 Fixed a speak: bug. It was lacking the double quotes which was ** causing problems. ** 01-25-97 Rewrote the quarterly routine. ** 01-28-97 Fixed a bug I made when I rewrote the quarterly routine. ** 01-30-97 Started work on the date range routine. ** Changed the TimeRange so it will now accept minutes. ** 02-09-97 added the hour wildcard '##' support. ie: '##:15'. AF1 (advanced feature #1) ** 02-11-97 Added the minute wildcard '##' support. ie '22:##' ** Added the Date wildcard support. ie: ##/##/## would be = DAILY ** ##/11/## would be = MONTHLY-11 ** 02/##/97 would be every day in FEB of 1997 ** 02-12-97 EZCrond can now auto update the daemon status window. ** If present, signals the EZCron (Prefs) program when starting/stoping. ** 02-13-97 Moved the timerange routine below the wildcard routines. ** Empty startdate and enddate fields are now '##/##/##' instead of '-' ** Empty starttime (rng1) and endtime (rng2) is now '--:--' rather than '-'. ** Renamed EZCron to EZCrond and EZCronGUI to EZCron. ** Sorry for the confusion, but they really needed renaming. ** The ARexx ports were also renamed to EZCROND and EZCRONPREFS. @endnode