- You will need to set up a cron to run the email script.  Something like:
	* * * * * /var/www/html/phpgroupware/calendar/cron

- I added the ability to add one alarm in the "Calendar - Add" screen
  so that the user does not have to submit the event and then go back
  and update the event just to get to the Alarm Management screen when
  the majority of the time they probably just want one email notification.
  The alarm fields do NOT show up when editing the event because if they
  want to edit an alarm they should use the Alarm Management screen.

- I added the ability to set an alarm on an event you are a participant of
  not just the events you are the owner of.

- rfc2445 implies multiple types of alarms (EMAIL, AUDIO, & DISPLAY) and
  the mysql table phpgw_cal_alarm does not have a field for 'type'.
  I have not implemented AUDIO & DISPLAY yet.

- rfc2445 implies the trigger can be a relative time or an absolute time
  so far I have only implemented relative time

- I do not use the 'text' field at this time because the cron message looks
  up and sends most of the information about the event in the email notification.

- I did not allow editing of an alarm since there is currently no text field
  and its easier just to remove and add a new alarm back in with a new
  relative time.

- If the time of an event is changed after an alarm is established the alarm does 
  not automatically change to the same relative time before the new event time.

- It would be nice if the text field were longer than 50 characters.

- It would be nice to add a preference for each user to set 
  the 'text' field so they don't have to type it in
  for each event.  The text field should allow some kind of replacement values 
  for SUBJECT, LOCATION, DESCRIPTION, START TIME, etc.

- I have not implemented repeating alarms, but I can see how it would
  be usefull to specify 'generate an email every 15 minutes for the
  hour before the event'.

- Alarms for repeating events get re-established by the cron for the
  next event for the same amount of time before the next event.  I am not sure
  what happens if the user edits/modifies/deletes a single event in the series???
   
- I am not sure what the intent of the 'enabled' field is? History?  The 
  database entry could just be removed when the alarm is generated.  For now
  I just disable it.