Summary


An event or to-do's summary is what is displayed in the main window. It is a brief overview of the item and is required. For an email alarm, the summary will be the subject of the email.

Description


The description is your chance to make a more complete entry for the event or to-do. The description is also used as the body of the message in an e-mail alarm. In a procedural alarm, the description is the command to be run. For procedural commands, the path must be an absolute path since BeThere does not inherit any path.

Due date/time


This is the time that the event or to-do is scheduled to happen. The time entered here is used to compute the times that alarms will go off. In an event, the field is labeled "Start Date" and "Start Time."

Location


An obvious one, this is where the event/to-do will take place.

Category


This field gives you a chance to define what kind of entry this is.

Security


The security level for the event/to-do. Public entries are stored in your public calendar directory, which may be on a shared file system so others can browse your calendars. Private calendar entries are stored in your private calendar directory, as are confidential entries. In the future confidential entries may be encrypted for further security.

Priority


How important this entry is, this is solely for informational purposes.

Status


The status of an entry can be changed from here. This is only for informational purposes, BeThere does not do anything with this field.

Attendees


These are people that will be attending the event or to-do. You can drag People files onto this window to add them to the attendee list automatically. For each attendee, a name and their email address is stored.

Alarms


Audio Alarms


An audio alarm will beep at the specified time.

DisplayAlarm


A display alarm will display a popup window with the event/to-do description as the text of the window.

Procedural Alarm


A procedural alarm is used to run a specified program at the given time. The program run and all of its arguments is given in the description field. The application to be run must be specified via an absolute path since the alarm_daemon does not inherit the PATH environment.

Mail Alarm


A mail alarm sends an email to the recipient when it goes off. The subject of the email will be the summary of the event or to-do, and the email body will be the description.

Recurrence Rules


Right now the only recurrence rule that can be applied is a daily rule. A value of 0 will mean that the event or to-do repeats forever, once is the default repeat rate.