@DataBase Daywatch.Guide
@Author Rand R. Fredricksen <rand@maui.netwave.net>
@Font Helvetica.font 13

@Index Index

@$VER: Daywatch.Guide V1.1.0 (02-Feb-97)
@Remark rf (02-Feb-97)
@(C) 1997 Explisit Soft!
@Macro Ver "V1.1.0"
@Macro _Contents "..............................@{FG Highlight}$1@{FG Text}@{Par}"
@Macro _Section "@{JLeft}@{LIndent 0}@{u}@{b} $1 @{ub}@{uu}@{LIndent 2}@{Par}@{Line}

@SmartWrap

@Node Main "Daywatch - AmigaGuide documentation"
@Font XCourier.font 13

@{JCenter}@{u}@{b} Table of contents @{uu}@{ub}

@{FG Highlight}___________________________________________________@{FG Text}

Welcome to the @{b}Daywatch @{Ver}@{ub} AmigaGuide,@{Par}
� 1996-97 by Allan Odgaard.@{Par}
@{FG Highlight}___________________________________________________@{FG Text}@{Par}
@{Line}@{JCenter}

If you have installed `SearchGuide' by G�rard Cornu,@{Line}
you can @{" Search " System C:Run >NIL: SearchGuide Daywatch.Guide} for a word or sentence in this guide.

@{JLeft}
@{Line}@{LIndent 2}

@{" New name     " Link Rename  } @{_Contents "What happend to Mayland?"}
@{Line}
@{" Introduction " Link Intro   } @{_Contents "What does Daywatch do?"}
@{" Disclaimer   " Link Disclaim} @{_Contents "What Daywatch can not do."}
@{" Registration " Link Register} @{_Contents "Is it not free?"}
@{" Author       " Link Author  } @{_Contents "Who should you write?"}
@{Line}
@{" Installation " Link Install } @{_Contents "How do I install Daywatch?"}
@{Line}
@{" Usage        " Link Usage   } @{_Contents "How should I use Daywatch?"}
@{" Hints        " Link Hints   } @{_Contents "How can I make Daywatch better?"}
@{" F.A.Q.       " Link FAQ     } @{_Contents "Frequently Asked Questions!"}
@{Line}
@{" History      " Link History } @{_Contents "Where the program has been!"}
@{" To Do        " Link ToDo    } @{_Contents "What can I expect?"}
@{" Credits      " Link Credits } @{_Contents "Who do I thank?"}
@{LIndent 0}
@{Par}@{LIndent 0}
@{JCenter}

This guide will not appear correctly if you do not have AmigaGuide_DT V40+

@EndNode

@Node Rename "Daywatch / What happend to Mayland?"


@{_Section "Mayland is dead, long live Daywatch!"}
I have recently been contacted by @{b}Mayland@{ub}(tm). Which, if you didn't know, is a Danish company which
sells calendars.


They didn't like my use of their name.


I have therefor changed it to Daywatch, which was suggested by Peter Wehle.

@EndNode

@Node Intro "Daywatch / Introduction"


@{_Section "Introduction"}
@{Line}
@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Disclaimer " Link Disclaim} What I cannot promise.
@{LIndent 2}
@{Par}


@{Pari 0}@{LIndent 0}@{b}@{u}Daywatch@{uu}@{ub} is a very useful @{b}Reminder program@{ub}, with features as follows:
@{Line}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Execute " Link Action} a command and/or show a message! Not only at the exact
event time, but also some minutes/hours/days before and after.
@{Line}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Come Again " Link DWD} feature of message requester.
@{Line}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Drag'n'Drop " Link Drag'n'Drop} events to quickly reschedule.
@{Line}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Year/Month/Day Calculations " Link Action} can be inserted in the message
text, e.g., "I'm %y-1976 years old!" will, unfortunately, always remind me of my correct age.
@{Line}@{LIndent 2}

@{Pari 0}@{LIndent 2}

@{b}@{u}Daywatch@{uu}@{ub} is also a very powerful @{b}Calendar program@{ub}, containing such features as:
@{Par}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Overview " Link MainWin} containing link buttons to the previous and next
months.
@{Par}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" Holidays " Link Holidays} can be defined, and are uniquely displayed in the
overview.
@{Par}@{LIndent 2}

@{Pari -9}@{LIndent 8}@{b} � @{ub}  @{" ARexx " Link ARexx} control.
@{Par}@{LIndent 2}



		@{" ---> Install... " Link Install}

@EndNode

@Node Disclaim "Daywatch / Disclaimer: Blah, blah, blah..."


@{_Section "Disclaimer"}
@{RIndent 3}

There is no warranty for this program to the extent permitted by applicable law. Except
where otherwise stated in writing the copyright holder and/or other parties provide the
program "as is" without warranty of any kind, either expressed or implied, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. The
entire risk as to the quality and performance of the program is with you. Should the program
prove defective, you assume the cost of all necessary service, repair, or correction.


In no event, unless required by applicable law or agreed to in writing, will any copyright
holder, or any other party who may redistribute the program as permitted above, be liable to
you for damages, including any general, special, incidental or consequential damages arising
out of the use or inability to use the program (including but not limited to loss of data or data
being rendered inaccurate or losses sustained by you or third parties or a failure of the
program to operate with any other programs), even if such holder or other party has been
advised of the possibility of such damages.


@WordWrap
@{JCenter}It is @{b}NOT@{ub} to be distributed on magazine coverdisks or similar without the owner's explicit written consent.@{JLeft}


@{JCenter}
Contact @{" Allan Odgaard " Link Author}, author.
@{JLeft}

@EndNode

@Node Register "Daywatch / Registration"


@{_Section "Registration"}
To register:


  (1) Fill out @{" this " Link Form} form.

  (2) Print out the form.

  (3) Place your signature on the form.

  (4) Send it along with 120DKK, US$20, 30DM or �15 to the @{" author. " Link Author}

  (5) Include any one of the following:

       a) EMail me your PGP key (if you have email).

       b) Include a Self Addressed Stamped Envelope (proper size and postage for a disk) and a diskette.

       c) Include the closest sensible equivalent of US$5 for a disk, postage, and handling.



Right now, the only way to pay is in cash (no coins).



A note about sending cash in the mail; make certain to disguise the money. If not, you can
bet that along the way someone will open it and take the money out -- it happens. Enclose the
cash in paper so the money cannot be seen when the envelope is held in front of a light. The
old "Hold it up to a light" trick is still popular :>


I cannot take responsibility for cash lost in the mail.



@{JCenter}
Upon receipt of payment I will create and forward your personal keyfile.

@{JLeft}



		@{" ---> Install " Link Install}

@EndNode

@Node Form "Registration form"
@Font courier.font 11
@WordWrap


@{_Section "Registration Form"}
I like Daywatch and I am willing to send you money for all your work!


Program/Version:  Daywatch/V1.1.0


           Name:

        Address:




          Email:

         Phone?:

PGP Fingerprint:


I agree to never distribute my personal keyfile.


_______________________________    ______________________

Signature                          Date


_________________________________________________________

City, Post Office, Country


I wish to make this program useful to as many people as possible. Please reformat
this as you wish. Use as much time and as many bytes as you can afford.


   Comments:


Suggestions:


  Questions:


   Problems:


@EndNode

@Node Author "Daywatch / Author"
@{Line}
@{_Section "Author"}
Daywatch was designed and programmed for the Amiga by:
@{Line}

	Allan Odgaard@{Par}
	Dagmarsgade 36@{Par}
	DK-2200 Copenhagen@{Par}
	EMail: Duff@DIKU.DK@{Par}
	http://www.DIKU.DK/students/duff/@{Par}
@{Line}

        @{" Register   " Link Register}        @{" ---> Install    " Link Install }        @{" Usage " Link Usage   }

@EndNode

@Node Install "Daywatch / Installation"


@{_Section "Installation"}
@{FG Highlight}Daywatch Requires:@{FG Text}
@{LIndent 5}

Kickstart V39 (OS 3.x) or above.

@{"MagicUserInterface" Link MUI} V3.1 or above.

@{"WBStart.Library" Link WBStart} V2.0+ (included!)
@{LIndent 2}


@{FG Highlight}Install Daywatch:@{FG Text}
@{LIndent 5}

Double-click on the install icon. Follow the prompts.
@{LIndent 2}


@{FG Highlight}Manual Installation:@{FG Text}
@{LIndent 5}

Copy or drag Prefs/DaywatchPrefs to Sys:Prefs/

Copy or drag WBStartUp/Daywatch to Sys:WBStartup/

Copy the catalog files you need to SYS:Locale/Catalogs/.

Copy one of the holiday files as EnvArc:Daywatch/Holidays@{LIndent 2}


@{FG Highlight}WBStart.library:@{FG Text}@{LIndent 5}

If you do not already have WBStart.Library by Stefan Becker, then you should copy this into Libs:.
@{LIndent 2}


@{FG Highlight}MUI:@{FG Text}@{LIndent 5}

If you do not have MUI you will have to download it from somewhere and install it.

The latest version on Aminet is 3.8. MUI is much too large to be included here.
@{LIndent 2}


@{FG Highlight}After Installation:@{FG Text}@{LIndent 5}

Modify the @{" tooltypes " Link ToolTypes} of Daywatch (@{b}not@{ub} DaywatchPrefs)



@EndNode

@Node Usage "Daywatch / Usage"
@WordWrap


@{_Section "Usage"}
   @{b}Daywatch@{ub}


	@{" Main Window " Link MainWin}

	@{" Drag'n'Drop " Link Drag'n'Drop}

		@{" The Menus " Link Menus}

	 	@{" Add/Edit Event Window " Link Event}

	 		@{" Before/After Time Window " Link Time}

	 		@{" Suspension List Window " Link List}

	 			@{" Add/Edit Suspension Window " Link Suspension}

	 	@{" Add/Edit Holiday Window " Link Holiday}



	@{" About Window " Link About}

	@{" ShowList Window " Link ShowList}

	@{" Settings Window " Link Settings}

	@{" Edit Template Window " Link Template}



  @{b}DaywatchDemon@{ub}



	@{" Message Window " Link DWD}

	@{" ARexx interface " Link ARexx}

	@{" ToolTypes " Link ToolTypes}


@EndNode

@Node MainWin "Main Window"


@{_Section "The Main Window"}
@{FG Highlight}Date Settings:@{FG Text}
@{LIndent 5} is the first framed group. Click on the day you would like to view. You may then Add, Edit, or
Remove an @{"event" Link Event} from the ListView.
@{LIndent 2}


@{FG Highlight}Text labels:@{FG Text}
@{LIndent 5} appear before the first of the month and after the last of the month.

These display some days in the previous and next months. These `labels' are link buttons and pressing them will go
backward or forward a month.
@{LIndent 2}


@{FG Highlight}Link buttons:@{FG Text}
@{LIndent 5} are also dropable, which means that you can just drop an event on it to
reschedule it to that day. See more in the @{" Drag'n'Drop " Link Drag'n'Drop} section.


@{LIndent 8}@{RIndent 6}If the linkbutton's text is hard to read due to fancy MUI background patterns, you
will want to reconfigure the text and background colors in the MUI @{" settings. " Link Settings}@{uu}
@{JLeft}
@{LIndent 2}@{RIndent 0}


@{FG Highlight}ListView:@{FG Text}
@{LIndent 5} On the right side of the main window you will see the ListView. This ListView shows the specified
day's events.
@{LIndent 2}



@{"Options" Link Options} Add, Edit, or Remove events.


@{"Holidays" Link Holidays} Modify holiday names.


@{"Menus" Link MenuA} Check out the menu items.


@EndNode


@Node Options "MainWindow/Options"}


@{_Section "Options"}
@{FG Highlight}Add:@{FG Text} an event@{LIndent 5} to the day by pressing "Add...". This will open the
@{" Add/Edit Event Window " Link Event}.

The values set in the @{b}time sliders@{ub} will be used as a starting point when you
add an event.
@{LIndent 2}


@{FG Highlight}Edit:@{FG Text}@{LIndent 5} an event by double-clicking it or by selecting it and
clicking "Edit...". This will open the @{" Add/Edit Event Window " Link Event}, and it will
contain the settings of the chosen event.
@{LIndent 2}


@{FG Highlight}Remove:@{FG Text}@{LIndent 5} events is also an option. Select the event to remove and
press "Remove", if the event appears more than once (like 15/3/?? would!), then a requester
will appear offering the options to remove it globally, or only today. If you choose to only
remove it today, then Daywatch will create a suspension for the selected day.

See more in the @{" suspension " Link Suspension} section.
@{LIndent 2}


@{FG Highlight}Drag:@{FG Text}@{LIndent 5} any event. You then drop the event onto a date
button (and the next link buttons). This will @{" reschedule " Link Drag'n'Drop} the event to that day. If
the event is weekly you will be asked whether to reschedule it globally or only in this week.
@{LIndent 2}

@EndNode

@Node Holidays "MainWindow / Holidays"}


@{_Section "Holidays"}
Notice that some of the date buttons might appear in a different color or have a
different text type and/or color (depending on the @{" settings. " Link Settings}) These days
are @{b}marked@{ub}. You, the user, are free to use the marking system for whatever you like.


Over the ListView is a text field, this contains the date in long form, e.g., "Friday the 4 of
July - 1997 (Week 14)". If the selected day is @{b}marked@{ub}, then this field will show
the name of this day (e.g., "Independence Day"). If you have associated more than one name to
a day arrows will allow you to browse through the different names.


To define or edit a day's name, click on the text above the ListView. This will open the
@{" holiday window " Link Holiday}.


If you would like to @{b}add a name@{ub} to a day that is marked already, use the
menu item "Add Holiday..." located in the "Edit" menu.
@{LIndent 0}

@EndNode

@Node MenuA "MainWindow/Menus"}


@{_Section "Other"}
@{LIndent 0} Also available from this window are the @{" menus. " Link Menus}

@{LIndent 0}

@EndNode

@Node Event "Add/Edit Event"


@{_Section "The Event Window:"}
Use this window to set everything that is relevant to an event.
@{LIndent 0}

         @{" Pattern " Link Pattern} is the first group; this group describes exactly when the
event shall happen.


        @{b} Time @{ub}
        @{b} Before @{ub}
        @{b} After @{ub}
        @{b} Suspensions @{ub}



         @{" Action " Link Action} describes what is to happen when the Event occurs.


        @{b} Name  @{ub}

        @{b} Message  @{ub}

        @{b} Command  @{ub}



         @{" Flags " Link Flags} are Event controls.


        @{b} Only nag once      @{ub}
        @{b} Delete after use   @{ub}

        @{b} Be polite          @{ub}
        @{b} Do after each boot @{ub}



Press   @{b}Done@{ub}   to close the window                       Press   @{b}Cancel@{ub}   to close the window

 and accept the changes you have made.                and discard the changes you have made.



@EndNode


@Node Pattern "Event Window/Pattern"


@{_Section "Pattern"}
First select the type of event by way of the cycle gadget.

Currently only two types are supported; @{b}Day(s)@{ub} & @{b}Date@{ub}.
@{LIndent 5}


@{LIndent 5}@{FG Highlight}Day(s)@{FG Text} is what you need when you want to be reminded of the event on specific
weekdays.


The Pattern will change to display the seven weekdays.

Press down all the weekdays on which the event occurs.
@{LIndent 5}



@{FG Highlight}Date@{FG Text}@{LIndent 5} should be selected if the event occurs on a date, whether
once in a lifetime, once every month, or once a year.

Pattern will show the day of the month, the month, and the year.


Deselect the fields that you do not want to specify; e.g., deselect the year field if the event
describes an annual event; e.g., a birthday or anniversary.


Select only the date to define an event which occurs on the same day every month, like a
loan payment or bank statement.


If the Event will occur only once leave all three fields selected.
@{LIndent 0}



@{b}@{u}Time@{uu}@{ub} 
@{LIndent 2}You need to specify what @{FG Highlight}Time@{FG Text} the event will happen. Use the
numeric buttons to set the hour and minute of the event.
@{LIndent 0}


@{b}@{u}Before@{uu}@{ub} 
@{LIndent 2}Now you may specify how long @{" Before " Link Time} the event occurs you wish
notification to occur (if at all).


Do this by pressing the "dd:hh:mm" gadget beside the "Before" label.


For example:
You have an event at 6:00 PM the 24/?-??.


If you would like be reminded four days before the event takes place, then set the Before
value to 4 days.
@{Line}If you do not wish to be notified before the event, set the Before value to zero.


The notification will be triggered either when the BeforeTime occurs, or when you next turn on the computer between Event Time -
Before and Event Time or Event Time + After (see below). In our example this would be
between the 20th and the 24th in each month.


If you would like to be notified every time you run Daywatch during the Before period set the
@{" Do After Each Boot " Link Flags} flag.


Be aware that if Before is greater than zero, you will be reminded of the event before the event and again at the event time.
@{LIndent 0}


@{b}@{u}After@{uu}@{ub} 
@{LIndent 2}You can also set an @{" After " Link Time} value. This will determine
how long after the event time the event will be remembered.


Daywatch uses this only when it is not running at the event time.


Set After to the length of the event when it comes to a movie you would like to see, since you
do not need to be notified after the movie has ended. For Mom's birthday you would set After
high, so you are certain to see it, even if you @{i}are@{ui} late to call (you @{b}BAD@{ub} boy :(


Let's again assume we have an event the 24th of something each year. We set the after to 5
days. Say you go on a holiday, and don't turn on your Amiga on the 24th. If the computer is next
turned on before or on the 29th, we would get a notification about the event.


If Daywatch is not started between the 24th and the 29th (event time + after)
then you will never be notified of the event.
@{LIndent 0}


@{b}@{u}Suspensions@{uu}@{ub} 
@{LIndent 2}The next gadget is @{FG Highlight}@{" Suspensions " Link List}@{FG Text}
This will open a window containing the list of Suspensions for this event.


Suspensions are for days on which the event would normally occur, but for some reason it
will not happen on one or more of these days. This is, of course, only useful for events that
occur on a regular schedule.


Let's say that we have to go to school Monday through Friday every week. We (well, I), of
course need Daywatch to remind us of this, so we create an Event that will do so.


Now what if we get a week off??? Then just add a Suspension that encompasses that week,
then the Event will be blocked during that period.


An easy way to create a Suspension is to select the day it is needed, select the event,
and click on remove (in the main window).
@{LIndent 0}


@EndNode

@Node Action "Event Window/Action"


@{_Section "Event Action"}
The event action is determined by three string gadgets.


@{FG Highlight}Name:@{FG Text}@{LIndent 5} This is the optional name of an event. This
name is used only in Daywatch's ListViews. You can have events without message text and
without a command to be executed. You will never be reminded of these events, but they will
appear in Daywatch's List.


Use the name field if you have set Daywatch to only execute a command, and would like to see
something meaningful in the ListViews.
@{LIndent 2}


@{FG Highlight}Message:@{FG Text}@{LIndent 5} This is an optional Message that will be
displayed when the event is triggered (see @{" DaywatchDemon " Link DWD} for more info
about the message-requester).


@{b}Calculations@{ub}@{LIndent 8} It is possible to do some date calculations
within the message field. For example, [%y (current year) - 1976] will compute my age. Daywatch
calculates the values to insert every time the message pops up, so they will always reflect my
current age.


Use the popup gadget next to the string gadget for a complete list of variables.


If you require that the result be changed from negative to positive then write %#(command
+/- number), e.g., "Only %#y-2000 years until the big New Years Eve...".
@{LIndent 2}


@{FG Highlight}Command:@{FG Text}@{LIndent 5} This is an optional command to execute
at the event time. The command will be executed asynchronously so there is no need to RUN
it. Use the WBStarter command for programs that have to be started from workbench. I
might include this feature in a later release.
@{LIndent 2}

@EndNode

@Node Flags "Event Window/Flags"


@{_Section "Flags"}
@{LIndent 5}@{FG Highlight}Only nag once:@{FG Text} Not currently implemented.@{LIndent 2}


@{LIndent 5}@{FG Highlight}Be Polite:@{FG Text} When checked, the message window will open in an inactive state,
this prevents the window from swallowing the keyboard presses. Also when BePolite is selected and the front most
screen is not public, then Daywatch will only flash the display instead of popping its screen to front.
@{LIndent 2}


@{LIndent 5}@{FG Highlight}Do After Each Boot:@{FG Text} If you check this flag, the event will popup every
time Daywatch is started between its EventTime - Before and EventTime. It is to be hoped that this is every
time you boot your Amiga :)
@{LIndent 2}


@{LIndent 5}@{FG Highlight}Delete After Use:@{FG Text} Setting this will delete the event from the list when
there is no longer a use for it. If you need Daywatch to tell you that the tea is done in 8 minutes, then you
probably want to check this flag :)
@{LIndent 2}

@EndNode

@Node Time "Before/After Time"


@{_Section "The Before/After Windows"}
These windows are 
�{
�|
�}
�~
�
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��ched to the event currently being edited.


You have the option to @{" add " Link Suspension} a new suspension to the event, @{" edit " Link Suspension} an
existing suspension or @{" remove " Link Suspension} a suspension.


@{LIndent 0}
@{b}Caution:@{ub}@{LIndent 5} If you have an event with the pattern "The 25 of April - 1997", and you add a
Suspension that has the same pattern, you will only find the Event in the @{" Show List " Link ShowList} window
(which you will find in the @{" menus " Link Menus}).
@{LIndent 0}



    @{" Suspension " Link Suspension}    @{" Usage " Link Usage}

@EndNode

@Node Suspension "Add/Edit Suspension"


@{_Section "The Suspension Window"}
The Suspension Window allows you to edit a suspension, the suspension can be a single day
or a range of days.


Closing the window means accepting the changes.


I apologize for the poor state of the edit-suspension system. I promise to radically enhance this.



    @{" Suspension List " Link List}    @{" Usage " Link Usage}

@EndNode

@Node Holiday "Add/Edit Holiday"


@{_Section "The Holiday Window"}
The first thing you will see in this window is a string gadget. Enter the name that you
would like displayed when the holiday is selected.


You do not have to limit yourself to using this only for holidays, it can be used for any
day you would like to highlight.


There are currently only two types of holidays available. The system will be much more
flexible in the future, but currently you have to settle for:


@{FG Highlight}Normal: @{FG Text}@{LIndent 8}
Use this if you want the day's name assigned to a specific day or range of days. These days
can occur every year or in only one year.@{LIndent 5}


@{FG Highlight}Advanced: @{FG Text}@{LIndent 8}
This is for using the day's name for a weekday that appears as the first, second...last of a
specific month, e.g., Mothers Day = "The second Sunday in May."
@{LIndent 5}@{LIndent 2}



    @{" Usage " Link Usage}    @{" Menus " Link Menus}    @{" Holidays " Link Holidays}

@EndNode

@Node About "About Window"


@{_Section "The About Window"}
This window shows the Mayland logo Dennis Sibera drew. It also shows the registered
owner of Daywatch.


If you hold the mouse over the "Registered to:" text, then a help-bubble will appear showing
some keyfile info like serial number, address, etc.


If you have not @{i}yet @{ui} registered Daywatch then you will get some alternative text...



    @{" Register " Link Register}    @{" Usage " Link Usage}

@EndNode

@Node ShowList "ShowList Window"


@{_Section "The ShowList Window"}
This window shows the entire list of events in chronological order.


You have two options, either @{" edit " Link Event} an event by pressing the "Edit..." button,
or remove an event by pressing the "Remove" button. Be aware that there is currently no
confirmation requester, and you cannot create suspensions from this window!



    @{" Usage " Link Usage}    @{" Menus " Link Menus}


@EndNode

@Node Settings "Settings"


@{_Section "The Settings Window"}
Besides the Save, Use, and Cancel, this window contains three groups. Let's start at the
top...


@{b}Links to previous and next month: @{ub}@{LIndent 5}


In this group you will find two cycle gadgets which control the background and text colors
for the linkbuttons.


This is because some people like fancy background patterns, which make the link button
text very hard to read. Use this to change it to more legible colors...
@{LIndent 2}


@{b}Holiday button look: @{ub}@{LIndent 5}


Define text style, color, and background of the `marked' days.


Be aware that italic does not work very well with most fonts.


The radio buttons control whether the background should stay as it is, change to a specific
color or be a bitmap.


The background will @{b}not@{ub} be different when the button is in a selected state.

	This is a limitation in MUI and there is currently nothing I can do to override it 8(
@{LIndent 2}


@{b}Miscellaneous flags:@{ub}
@{LIndent 5}

@{FG Highlight}Show week numbers:@{FG Text}@{LIndent 8} Choose to show the week numbers (located
to the left of the date buttons) or not.
@{LIndent 5}

@{FG Highlight}Use AM/PM:@{FG Text}@{LIndent 8} Enable this if you would like to see Daywatch make
use of the 12 hour clock format... you will still find the 24 hours clock used in the
@{" Edit Event " Link Event} window for now.
@{LIndent 5}

@{FG Highlight}Show dates compact:@{FG Text}@{LIndent 8} This will set the group spacing to zero for
the group that contains the date buttons. Some might prefer this look and some PAL users
might use it for the space that it saves them!
@{LIndent 5}

@{FG Highlight}Confirm list save:@{FG Text}@{LIndent 8} Whenever you close DaywatchPrefs, Daywatch
will check for changes to the eventlist, and save it if there are. If Confirm is enabled, then
DWP will ask you before saving the list, giving you the option of discarding the changes.
@{LIndent 2}


    @{" Usage " Link Usage}    @{" Hints " Link Hints}


@EndNode

@Node Template "Edit Template"


@{_Section "The EditTemplate Window"}
This window is exactly the same as the @{" Add/Edit Event " Link Event} window. And with
good reason!


When you select "Done", the before and after times, and the checkmark states will be saved
and used as a template when you add a new event.



    @{" Usage " Link Usage}    @{" Menus " Link Menus}


@EndNode

@Node Menus "The Menus"

@{_Section "Menus"}@{LIndent 0}
@{b}Project		Edit			Location		Settings@{ub}


@{"About..." Link Menus 18}		@{"Cut" Link Menus 27}			@{"Go to today" Link Menus 48}	@{"Settings..." Link Menus 52}

@{"About MUI..." Link Menus 20}	@{"Copy" Link Menus 29}					@{"GUI Settings..." Link Menus 54}

~~~~~~~~~~	@{"Paste" Link Menus 30}					~~~~~~~~~~~~

@{"Quit" Link Menus 23}			~~~~~~~~~~~				@{"Edit template" Link Menus 57}

			@{"Show list..." Link Menus 35}

			@{"Clear list" Link Menus 38}

			~~~~~~~~~~~

			@{"Add holiday..." Link Menus 40}



@{b}@{u}PROJECT MENU:@{uu}@{ub}
@{LIndent 0}

@{LIndent 2}@{FG Highlight}About:@{FG Text} This will open the Daywatch @{" about window. " Link About}
@{LIndent 0}

@{LIndent 2}@{FG Highlight}About MUI:@{FG Text} Brings up the @{" MUI " Link MUI} about requester, this holds the MUI version,
copyright notice, etc.
@{LIndent 0}

~~~~~~~~~~

@{LIndent 2}@{FG Highlight}Quit:@{FG Text} This will close the DaywatchPrefs window.
@{LIndent 0}


@{LIndent 2}@{b}@{u}EDIT MENU:@{uu}@{ub}
@{LIndent 0}

@{LIndent 2}@{FG Highlight}Cut:@{FG Text} This will remove the selected event from the list and keep it on the internal
clipboard.
@{LIndent 0}

@{LIndent 2}@{FG Highlight}Copy:@{FG Text} This copies the selected event to the internal clipboard.
@{LIndent 0}

@{LIndent 2}@{FG Highlight}Paste:@{FG Text} This will insert the event stored on the clipboard. Be aware that the new event
will not have any suspensions and it will only be assigned to the current day.
@{LIndent 0}

~~~~~~~~~~

@{LIndent 2}@{FG Highlight}Show list:@{FG Text} This will open a @{" window " Link ShowList} which displays the complete list
of events. The events are sorted chronologically.
@{LIndent 0}

@{LIndent 2}@{FG Highlight}Clear list:@{FG Text} To clear all events. For professional use only.
@{LIndent 0}

~~~~~~~~~~

@{LIndent 2}@{FG Highlight}Add holiday:@{FG Text} If you would like to assign a name to the selected day, and mark the day in
the overview, selecting this menu item will open the @{" Add/Edit Holiday window " Link Holiday}.

Normally, you would just click on the text over the ListView (in the main window) to accomplish this.

If a day already has a name and you would like an additional name assigned to it, then you must use this menu item.
@{LIndent 0}


@{b}@{u}LOCATION MENU:@{uu}@{ub}

@{LIndent 2}@{FG Highlight}Go to today:@{FG Text} Resets the date and sliders to now.
@{LIndent 0}


@{b}@{u}SETTINGS MENU:@{uu}@{ub}

@{LIndent 2}@{FG Highlight}Settings:@{FG Text} Open the @{" settings window " Link Settings} to configure Daywatch specific
variables.
@{LIndent 0}

@{LIndent 2}@{FG Highlight}GUI Settings:@{FG Text} Open the @{" MUI " Link MUI} settings window. Here you can totally
customize the look of Daywatch. These settings will not be saved unless you are using a registered version of MUI,
but you knew that, didn't you? Well, now you know.
@{LIndent 0}

~~~~~~~~~~

@{LIndent 2}@{FG Highlight}Edit template:@{FG Text} Open the @{" Add/Edit event window " Link Event}. Enter
the settings you would like to be used as a template each time you define a new event.
@{LIndent 0}


@EndNode


@Node Drag'n'Drop "Drag'n'Drop"


@{_Section "Drag'n'Drop"}
In Daywatch you are able to @{b}drag@{ub} events. You can
@{b}drop@{ub} them onto the date buttons (and linkbuttons) to reschedule
events quickly.


If you Drag'N'Drop an event which happens @{b}weekly@{ub} (e.g., each Tuesday) you will
be asked if the change should happen globally, or only this week.


@{" Usage " Link Usage}

@EndNode

@Node ARexx "Daywatch / ARexx"


@{_Section "ARexx"}
Portname = DAYWATCH@{LIndent 0}


@{FG Highlight}Command:@{FG Text}	AddDate

@{FG Highlight}@{LIndent 18}Template:@{FG Text}	Day/N, Month/N, Year/N, Hours/N,
Minutes/N, Before/K/N, After/K/N, Name/K, Message/K, Command/K, BP=BePolite/S,
DAU=DeleteAfterUse/S, DAEB=DoAfterEachBoot/S.
@{LIndent 0}

@{FG Highlight}Example:@{FG Text}	AddDate 24 9 96 23 45 before 1 after 120 name '"ItsLate"' message '"Go to Bed!"' BP
@{LIndent 2}


This command will add a new event to the current list of events.

If you do not supply @{b}Day@{ub}, @{b}Month@{ub}, @{b}Year@{ub}, @{b}Hour@{ub}, or
@{b}Minute@{ub}, current values will be substituted.

Set @{b}Day@{ub}, @{b}Month@{ub}, or @{b}Year@{ub} to zero for wildcard use.

The @{b}Year@{ub} can be expressed with 2 or 4 digits (this goes for all the commands.)


@{b}Before@{ub} and @{b}After@{ub} are parsed as minutes; default values are 0 and 120,
respectively.

By default no @{b}Flags@{ub} are set.
@{LIndent 0}


@{FG Highlight}Command:@{FG Text}	AddDays

@{FG Highlight}@{LIndent 18}Template:@{FG Text}	Mon=Monday/S, Tue=Tuesday/S,
Wed=Wednesday/S, Thu=Thursday/S, Fri=Friday/S, Sat=Saturday/S, Sun=Sunday/S,
Hours/N, Minutes/N, Before/K/N, After/K/N, Name/K, Message/K, Command/K,
BP=BePolite/S, DAU=DeleteAfterUse/S, DAEB=DoAfterEachBoot/S.
@{LIndent 0}

@{FG Highlight}Example:@{FG Text}	AddDays Tue 24 30 name '"Late!"' message '"Wake up!"'
@{LIndent 2}


This command will add an event to the list of events, you must supply at least one day. See
@{b}AddDate@{ub} for further explanation...
@{LIndent 0}


@{FG Highlight}Command:@{FG Text}	DateToSeconds

@{FG Highlight}@{LIndent 18}Template:@{FG Text}	Day/N, Month/N, Year/N, Hours/N,
Minutes/N.
@{LIndent 0}

@{FG Highlight}Examples:@{FG Text}	DateToSeconds

		 -> RESULT=591133020 RC=0

		DateToSeconds 1 1 78 0 0

		 -> RESULT=0 RC=0
@{LIndent 2}


This command will convert the specified date string to seconds since January the 1st, 1978.
Specify a zero for @{b}Day@{ub}, @{b}Month@{ub} or @{b}Year@{ub} if you would like to
substitute the current time. Missing arguments will also be replaced with current values.

Be aware that 14 is a valid @{b}Month@{ub} value and 41 is a valid @{b}Day@{ub} value, this
is useful for, e.g., adding 8 months and 15 days to a date! The result of this command can be
used as argument for the @{b}SecondsToDate@{ub} command.
@{LIndent 0}


@{FG Highlight}Command:@{FG Text}	SecondsToDate

@{FG Highlight}@{LIndent 18}Template:@{FG Text}	Seconds/N.
@{LIndent 0}

@{FG Highlight}Examples:@{FG Text}	SecondsToDate

		 -> RESULT="24 9 1996 19 40" RC=0

		SecondsToDate 0

		 -> RESULT="1 1 1978 00 00"  RC=0
@{LIndent 2}


This command will convert the specified number of @{b}Seconds@{ub} into a numeric date
string. Without an argument, this will return the current date. The result of this command
can be used as an argument for the @{b}DateToSeconds@{ub} command.
@{LIndent 0}


@{FG Highlight}Command:@{FG Text}	Quit

@{FG Highlight}@{LIndent 18}Template:@{FG Text}	(none)
@{LIndent 0}

@{FG Highlight}Example:@{FG Text}	Quit
@{LIndent 2}


This sucks, and will blow up your computer :)
@{LIndent 0}



@{b}Note:@{LIndent 5}@{ub} When passing a string which contains spaces to Daywatch via arexx, you must
surround it with both quotes (') and double quotes ("). The arexx interpreter removes the
outside pair before sending the string to Daywatch.
@{LIndent 0}


@{b}@{LIndent 18}Example:@{ub} AddDays Tue 24 30 name '"Late!"' message '"Wake up!"'
@{LIndent 0}



    @{" Usage " Link Usage}


@EndNode


@Node DWD "Daywatch Demon"


@{_Section "The Message Window"}
The @{FG Highlight}Time Line@{FG Text}@{LIndent 5} is at the top of this window. This displays the current time,
day and date.
@{LIndent 2}


The @{FG Highlight}Pattern@{FG Text}@{LIndent 5} of the event is next. This shows when the event is scheduled,
e.g., "12:00, Mon" or "15:30, 17-Mar-??", etc. This line will appear in one of three colors:
@{LIndent 8}


@{FG Text}Text@{FG Text}		= The event is soon to come (this is a pre-warning)

@{FG Highlight}Highlight@{FG Text}	= The event is starting/happening right now!

@{FG Fill}Fill@{FG Text}		= This is a `Come Again' event (see below for more
explanation).
@{LIndent 2}


@{FG Highlight}ListView: @{FG Text}@{LIndent 5} displays the message.
@{LIndent 2}


@{FG Highlight}Come Again: @{FG Text}@{LIndent 5}
Under the ListView is a check box which decides whether you would like this event to @{b}reappear@{ub} after n
units. Edit the number of units in the string gadget and select the units to use with the cycle gadget. Notice
that pressing the mouse on the text will toggle the check mark and pressing return in the string gadget or using
the arrow gadget will mark the check box.
@{LIndent 2}


@{FG Highlight}Proceed: @{FG Text}@{LIndent 5}
@{b}Do what you are told@{ub}, then close the reminder window.
@{LIndent 2}


@{FG Highlight}Delete Event: @{FG Text}@{LIndent 5}
Delete this event from the list. If you have selected the `Come Again' check mark,
then the event @{b}will@{ub} come again, but the event will not be found in DaywatchPrefs.
@{LIndent 2}



    @{" Usage " Link Usage}

@EndNode

@Node ToolTypes "Daywatch Tooltypes"


@{_Section "ToolTypes"}
Several ToolTypes exist for Daywatch (not @{i}DaywatchPrefs@{ui})
@{LIndent 5}


@{FG Highlight}AMPM_Mode:@{FG Text}@{LIndent 8} This is a switch, set it if you want a 12 hour clock.
@{LIndent 5}


@{FG Highlight}CX_PopKey:@{FG Text}@{LIndent 8} Defines the hotkey sequence that will invoke DaywatchPrefs (defaults to `LAlt Ctrl m').
@{LIndent 5}


@{FG Highlight}DoNotWait:@{FG Text}@{LIndent 8} This is used by Workbench, set this if you put Daywatch in Sys:WBStartup/ (which is recommended).
@{LIndent 5}


@{FG Highlight}OutPutWin:@{FG Text}@{LIndent 8} Define the output of executed commands, this could be NIL: to avoid output (defaults to `OutPutWin=Con:000/164/528/198/Daywatch Output.../Auto/Close/InActive/Wait').
@{LIndent 5}


@{FG Highlight}Prefs:@{FG Text}@{LIndent 8} The name and path of DaywatchPrefs (defaults to `Sys:Prefs/DaywatchPrefs').
@{LIndent 5}


@{FG Highlight}TimeBackAction:@{FG Text}@{LIndent 8} When Daywatch is started it will read the system time. If this
is less than what it was the last time DWD was running, DWD will run the command specified here. This is very handy
if your Amiga `forgets' the time whenever a serious crash occurs (defaults to `Sys:Prefs/Time').
@{LIndent 2}



   @{" Usage " Link Usage}	@{" Table of Contents " Link Main}


@EndNode

@Node Hints "Daywatch / Hints"


@{_Section "Hints"}
Enter MUIPrefs and set the ListView Leading (on the ListView-Page!) to something high.
This makes the event ListView look much better.


Please forward anything you find useful.



    @{" Allan Odgaard " Link Author}    @{" Register " Link Register}    @{" Table of Contents " Link Main}


@EndNode

@Node FAQ "Daywatch / F.A.Q."


@{_Section "FAQ"}
@{FG Highlight}18-Jun-96:@{FG Text}@{LIndent 5}


DWD = Daywatch (DaywatchDemon)

DWP = DaywatchPrefs


@{b}Q:@{ub} @{LIndent 8}DWP sometimes crash with guru 8000 0004???
@{LIndent 5}


@{b}A:@{ub} @{LIndent 8}With fancy MUI settings (like backgrounds, etc.) this is known to
happen. Increase the stack of DWP, everything should work fine :)
@{LIndent 5}@{LIndent 2}



   @{" Allan Odgaard " Link Author}    @{" Register " Link Register}    @{" Table of Contents " Link Main}


@EndNode

@Node History "Daywatch / History"


@{_Section "History"}
@{FG Highlight}V1.1.0 (24-Mar-97)@{FG Text}@{LIndent 5}


Added catalogs for Italy & The Nederlands.

The French catalog has been updated a little.

Added even more catalogs from ATO.


Icons where enhanced by Roman Patzner.


Changed the version numbering system to "Major.Minor.Beta."

Beta versions can be found at my @{" homepage. " Link Author}


Removing events from the global event-listview didn't cause the Edit & Remove gadgets to be ghosted.


When DaywatchDemon is first started, then it will ignore the "Be Polite" flag.

			@{i}Marcin Orlowski @{ui}


The installer script will nolonger ask for an 68020, since the program now works on a plain 68000

			@{i}Kaikumaa Timo @{ui}


Fixed a bug in DaywatchDemon which would cause it to only show "Do after each boot" events once, @{b}if@{ub} they
where set to only appear on a specific date.

			@{i}Georges Goncalves @{ui}


Pressing a link button which should link to a date in the next month, would go to the previous month,
@{b}if@{ub} the pressed link was after the 11th day of a month.


@{" � " Link ARexx}@{LIndent 8} Changed the ARexx portname to DAYWATCH instead of MaylandRexx. This is more
styleguide compliant.@{LIndent 5}


@{" � " Link Author}@{LIndent 8} Changed my homepage URL and added my new email address.@{LIndent 5}


@{" � " Link Register}@{LIndent 8} Lowered the german shareware fee to 30DM since this more closely equals 120DKR.
@{LIndent 5}


@{" � " Link Rename}@{LIndent 8} Changed the programs name to Daywatch.
@{LIndent 2}



@{FG Highlight}V1.0 (7-Oct-96)@{FG Text}@{LIndent 5}


@{b}First release.@{ub}


@EndNode

@Node ToDo "Daywatch / To Do"


@{_Section "To Do"}
Daywatch's future looks something like this:


� MultiSelect in some of the ListViews.

� Keep the cursor when removing events.


� Horizontal-scrolling ListView in main window


� Suspension editing should be improved (work like the Holidays system).

� Make an `Optimize' button, which would join suspensions to one ranged susp.


� Different color settings for different holiday types.


� Holiday and EventFile should be in ASCII.


� Much better holiday definition.


� @{LIndent 5}PopUp gadget in front of Command string gadget, pops up a
predefined list of often used commands. @{LIndent 2}


� Make the Test button work.


� Use real sliders for the EventTime (in the EditEvent window).


� When removing an event, there should be an option to create a "suspension-range."

� Also a gadget saying "from today" causing the event to be removed today and to the end of
time...


� PopUp gadget in EventPattern's Date group (to change the date.)

� Give a string gadget in the Day(s) group to choose every n week.

� Make a new group/type of event which should be every n day.


� @{LIndent 5}Make an *OPTIONAL* navigation panel under the date buttons,
this would let you step 1 day, week, month or year. @{LIndent 2}


� @{LIndent 5}If the selected day is a holiday, then it should have another
background (as in the unselected state) - there are currently some
limitations in MUI... @{LIndent 2}


� More `Location'-menuitems! (go to week, date, year etc.)


� @{LIndent 5}Have two submenus which are: `Go to next' & `Go to previous'.
Events can then be set to appear in these menus, e.g., "Go to next /
Phonebill" would select the next appearance of the `Phonebill' event!
@{LIndent 2}


� @{LIndent 5}Possibility to optimize the EventList, like deleting old
events/suspensions, joining suspensions that could just as well be a range,
etc... @{LIndent 2}


� Make all the Date buttons dragable, and drop them whereever a date can be adjusted.


� Have as many windows open as the user wants.


� @{LIndent 5}Optionally create a suspension when adding a new event, e.g. if
today is Tuesday the 3 of July 1996, then (if enabled in prefs) when you add
an event to today (which will occur more than once, like each Tuesday), this
event will be `born' with the suspension 1.1.76-2.7.96. @{LIndent 2}


� LinkButtons should have "RealVerify" instead of "Immediate."


� Create a taskmanager.


� `Search'-button in the ShowList window.


� Some kind of info requester showing how many events are on the list etc.


� @{LIndent 5}Show full moon (perhaps also half-full!), probably as an
*optional* image in the day-name (holiday) text display. Also mark these days
in the month overview. @{LIndent 2}


� Optional time-out value of event-requester. (setable for each event)


� Extra command type in message text, this would be something like:

@{LIndent 5}%{dd/mm/yyyy} - This would insert the number of days/months/years until the
specified day.

@{LIndent 8}E.g., "Turn in paper in %{25/1/1996} days"

     "There is %{/12/1996} months until Xmas"

     "Let's celebrate year 2000, after all, there are only %{//2000} years until it..."
@{LIndent 2}


� MUCH more keyboard support in the "Daywatch Eventer"-window.


� @{LIndent 5}Attach a menu to the message window, this should let you reschedule the
event, or maybe just bring up DaywatchPrefs.
@{LIndent 2}


� Indicate, in the message popup-win, that an event has the DAEB flag set.


� Some kind of a show pattern in the "ShowList Window"


� DisplayAlert() flag for each event.


@{LIndent 5}� Show events for the next day, for example, until 04:00, after
todays events. Use a seperator or show them in another color. @{LIndent 2}


� Make the `Time' string in the event requester a `live'-clock!


� Make multiple Before values. Perhaps also set a step value.


� @{LIndent 5}Let the user set a `ComeAgain' time, which instead of `in 15 minutes' would
be an exact time like `at 20:35 in 0 days'@{LIndent 2}


    @{" Allan Odgaard " Link Author}    @{" Register " Link Register}    @{" Table of Contents " Link Main}


@EndNode

@Node Credits "Daywatch / Credits"


@{_Section "Credits"}
My sincere thanks go out to:@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Denni Sibera for his great Daywatch logo and the icon
enhancement!@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Dirk Federlein for his help and kind replies.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Eberhard Hafermalz for the German catalog files, German holiday
file, beta testing, and ideas.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Georges Goncalves for the french translation, french holiday file,
beta testing, and ideas.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Kai Hofmann for his bugreports.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Mads Henriksen for OrgAsm - I wonder when the public will see
it?@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Mads Jensen for the Danish holiday file.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Rand Fredricksen for helping me understand the strange
American way of doing things, the American holiday files, ideas, questions, beta testing, and
the American.guide file.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Stefan Becker for @{" WBStart.Library " Link WBStart}
@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Stefan Stuntz for @{" MUI " Link MUI}@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Christopher A. Loewe for his indepth testing.@{LIndent 2}


@{b}�@{ub} @{LIndent 5}Riccard Linde for his lovely AWN-logo.@{LIndent 2}


@{LIndent 0}
@{JCenter}
@{i}And last, but not least, all the fine people at @{b}Commodore@{ub}  for the Amiga...@{ui}
@{JLeft}

@EndNode


@Node WBStart "WBStart.Library"

@{JCenter}@{b}WBStart.Library V2.1@{ub}


� 1991-96 by Stefan Becker

@{JLeft}
WBStart is a package to emulate the Workbenchs' method of starting programs.
Emulating this method seems to be easy on the first look, because you only have to load a
program, create a process and then send a Workbench startup message to it.


But complications arise from this startup message. It contains pointers to memory and
directory locks owned by your process and it will not be returned until the newly created
Workbench process exits. So your process can't quit until ALL Workbench processes which
have been started by your process are finished. If you don't wait the replied messages will go
into nowhere land and the man from India will visit you.


WBStart solves this problem by using a handler process, which loads the program, creates
the process, sends the message and then waits for the reply. You just supply all needed
information like program name and arguments in a library call. The handler copies this
information so your program can free its resources and exit.



The complete package can be obtained at
@{FGHighlight}"AmiNet:util/libs/WBStart.lha"@{FG Text}

@EndNode


@Node MUI "MUI - MagicUserInterface"

@{JCenter}@{b}MUI - MagicUserInterface@{ub}


� 1993/96 by Stefan Stuntz

@{JLeft}
MUI is a system to generate and maintain graphical user interfaces. With the aid of a
preferences program, the user of an application has the ability to customize the outfit
according to his personal taste.

MUI is distributed as shareware. To obtain a complete package containing lots of examples
and more information about registration please look for a file called "muiXXusr.lha" (XX
means the latest version number) on your local bulletin boards or on public domain disks.


@{JCenter}If you want to register directly, feel free to send


DM 30.-  or  US$ 20.-


to


Stefan Stuntz

Eduard-Spranger-Stra�e 7

80935 M�nchen

GERMANY

@{JLeft}
@EndNode

@node Index

 Index created by AGIX 1.2 (5.8.94) Copyright � Ralph Seichter

 -


 A


 @{"About Window" Link About}

 @{"Action" Link Action}

 @{"Add/Edit Event" Link Event}

 @{"Add/Edit Event Window" Link Event}

 @{"Add/Edit Holiday Window" Link Holiday}

 @{"Add/Edit Suspension Window" Link Suspension}

 @{"Address" Link Author}

 @{"After" Link Time}

 @{"Allan Odgaard" Link Author}

 @{"ARexx" Link ARexx}

 @{"Author" Link Author  }


 B


 @{"Before" Link Time}

 @{"Before/After" Link Pattern}

 @{"Before/After Time Window" Link Time}


 C


 @{"Calculations" Link Action}

 @{"Come Again" Link DWD}

 @{"Credits" Link Credits }


 D


 @{"Disclaimer" Link Disclaim}

 @{"Do After Each Boot" Link Flags}

 @{"Drag'n'Drop" Link Drag'n'Drop}


 E


 @{"Edit Event" Link Event}

 @{"Edit Template Window" Link Template}

 @{"Edit Suspension" Link Suspension}

 @{"Event" Link Event}

 @{"Execute" Link Action}


 F


 @{"F.A.Q." Link FAQ     }

 @{"Flags" Link Flags}

 @{"Free Key!" Link FreeKey }


 H


 @{"Hints" Link Hints   }

 @{"History" Link History }

 @{"Holidays" Link Holidays}

 @{"Holiday Window" Link Holiday}


 I


 @{"Install" Link Install }

 @{"Installation" Link Install }

 @{"Introduction" Link Intro   }


 M


 @{"MagicUserInterface" Link MUI}

 @{"Main Window" Link MainWin}

 @{"DaywatchDemon" Link DWD}

 @{"Me (Allan Odgaard)" Link Author}

 @{"Menus" Link MenuA}

 @{"The Menus" Link Menus}

 @{"Message Window" Link DWD}

 @{"MUI" Link MUI}


 O


 @{"Options" Link Options}

 @{"Overview" Link MainWin}


 P


 @{"Pattern" Link Pattern}


 R


 @{"Register" Link Register}

 @{"Registration" Link Register}

 @{"Remove" Link Suspension}

 @{"Reschedule" Link Drag'n'Drop}


 S


 @{"Search" System C:Run >NIL: SearchGuide Daywatch.Guide}

 @{"Settings" Link Settings}

 @{"Settings Window" Link Settings}

 @{"Show List" Link ShowList}

 @{"ShowList Window" Link ShowList}

 @{"Suspension" Link Suspension}

 @{"Suspensions" Link List}

 @{"Suspension List" Link List}

 @{"Suspension List Window" Link List}


 T


 @{"Table of Contents" Link Main}

 @{"To Do" Link ToDo    }

 @{"Tooltypes" Link ToolTypes}


 U


 @{"Usage" Link Usage}


 W


 @{"WBStart.Library" Link WBStart}

 @{"Window" Link ShowList}


 Y


 @{"Year/Month/Day Calculations" Link Action}



@endnode

@Node Rand "Daywatch / Rand"

@{u}@{b}Rand Fredricksen@{ub}@{uu}

Chicago, USA


Allan and I have been corresponding for about six months. The trouble began when I mailed
a postcard to him because I found DefProtect useful. DefProtect is a program Duff wrote to
direct AmigaDOS to automatically set protection bits in specified Volumes/ Directories/
Files for people using MultiUser.


@{b}BTW:@{ub} If you use @{u}any@{uu} publicly released programs, please take a minute to mail the author.


Duff sent email to thank me for the postcard, and asked if I would beta-test his newest
effort, this program he calls Daywatch. It's a reminder program, as you must know by now. I
explained to him that I could help him with his English in the doc files, but I did not have
time to test any new programs.


Being the nice guy that I am, I agreed that he could send it to me, and that I would have a look.


Well, this turned into that, and before I knew it I was regularly using Daywatch, and criticizing
Duff's program on a regular basis.


This .guide is the result of my tinkering with Duff's original English Daywatch.guide. You will
also find my fingerprints on the American Holidays file, in the Program Strings, and in the
Help Bubbles.


Speaking of fingerprints, my PGP 'print is

4E 67 4C 3E 93 28 6C 88   10 41 A2 CB 53 55 8C 17.

My PGP key is available from me or through public servers.


So you can direct comments about this .guide to me (but you are free to send praise about
this .guide to Duff ;)

I had no idea how long this .guide thing was going to take; I know there is still room for
improvement.

But, if you think this .guide is good, and you would like me to look at your
.guide, perhaps in exchange for a .keyfile, please email me.


I must say I enjoy conversing with Allan; as much as we have talked about Daywatch, we discuss
other Amiga programs, Amiga hardware, and our work and personal lives.

Because of this I have a better understanding of people, especially Amiga users :)


Thanks Duff,

 - Rand

 rand@maui.netwave.net



    @{" Allan Odgaard " Link Author}    @{" Register " Link Register}    @{" Table of Contents " Link Main}


@EndNode