PIM: Calendar
Functional Description
The Calendar application allows a user to plan their schedule. This includes the scheduling of timed events such as meetings,
day events such as birthdays, and multi-day events such as workshops. The application also provides the facility to set alarms for events and to specify a pattern of repetition for events.
Features
It is possible to add events to the Calendar.
Alarmed events sound or display an alarm at the
specified time. The Calendar application does not need to be running in order for the alarm to sound.
It is possible to specify events as taking all day. These
events are not affected by timezone changes.
It is possible to beam events to or from another device using Bluetooth, IR, and other mechanisms supported by the QtopiaSendVia mechanism.
It is possible to view the events in the following ways:
- The events for a single day.
- The events for a single month.
- A detailed view of a single event.
- An event opened for editing.
Day View
This shows the events that occur for a particular date. Repeating events are shown in pale blue and non-repeating events are shown in pale red. All day events are shown at the top of the view.
The view also adjusts the height of hours through the
day to show as much detail of the events for that day as possible.
The user is able to navigate to other days by typing that date on the phone keypad, or by using the left and right cursor keys.
The user is able to edit the general settings such as the default alarm preset and the default day start time.
The user is able to change to the month view, a detailed view of the current event or add a new event.
Month View
This shows the events that occur for a particular month. Repeating events are shown in blue, non-repeating events in red.
The month view is drawn so that an approximate indication of when events occur within the month is presented.
The user is able to navigate to other days by typing that date on the phone keypad, or by using the cursor keys.
The user is able to edit the general settings such as the default alarm preset and the default day start time.
The user is also able to show the details for a particular day or add a new event.
Detailed View
The detailed view of an event displays the data for a single event. This is shown as rich text. All the information for the event is shown formatted for optimum readability.
From the detailed list view the user is able to:
- Edit the current event, using the Edit view of the event.
- Delete the current event.
- Beam the current event via IR.
Edit View
The edit view of an event allows the user to specify the data for a new event
or modify that of an existing event.
Non-applicable values are disabled. For example, the start time entry are disabled if the event is marked as an all day event.
When the editing has been completed the user is able to either accept or cancel the changes they have made.
It is possible to configure the day view to display
events starting from a particular time.
An event consists of the following:
- A single line text description.
- A single line text location.
- A multi-line text note.
- A start date and time.
- An end date and time.
- A timezone for start and end times. This is only available where the event is associated with a timezone.
- A pattern of repetition.
- An alarm, including if it is audible and how long before the event it is to be activated.
- One or more categories. If the event is not assigned any category it is categorized as unfiled.
It is possible to delete events. The user is prompted to verify the deletion of an event.
If an occurrence of a repeating event is deleted then the user is asked if they mean to delete just that occurrence, all of the future events for that sequence, all of the preceding events for that sequence, or the entire sequence.
It is possible to modify events.
If an occurrence of a repeating event is modified, the user is prompted to indicate if they mean to modify just that occurrence, all of the following events for that sequence, all preceding events for that sequence, or the entire sequence.
- If a task has a due date, the calendar application shows the task on that due date (similar in appearance to an all day event). In addition, tasks can be scheduled as recurring tasks, and they are then marked as "due" on each particular recurrence. If a recurring task has been completed, it is returned to the incomplete state on the day following the existing due date and assigned a new due date based on the recurrence rule.
- The tasks application is still the main point of entry for tasks, and selecting a task from the calendar application simply instructs the tasks application to display that task.
- Tasks can have reminders set for them some period before the due date.
Navigation between dates and events is easy and clear and the date is visible at all times.
The user is able to set an event to: repeat daily, weekly, monthly, yearly or other. These are standard patterns of repetition and the user is able to create a more complex pattern using the advanced options.
These repeat patterns are not guaranteed to be maintained when syncing to non-Qt Extended devices or software.
Daily
These events happen once each day. In the advanced options the user is able to specify the number of days between each occurrence of the event.
Weekly
These events happen once each week. In the advanced options the user is able to specify the number of weeks between repetitions, as well as specifying that an event occurs on multiple days of a week. The date
of the starting day for an event is always the first day the event will
occur in a week. Therefore an event occurring every four weeks on Wednesday,
Friday, and Monday occurs on the Wednesday, then the Friday of that week and the immediately following Monday, and then does not re-occur until the forth Wednesday following that.
Monthly
These events happen once each month on the same day of month as the start event.
In the advanced options the user is able to specify how many months apart each repeating event will occur.
It is also possible to specify that the event:
- Occurs on a specific day of the month. For example, every 2 months on the 18th of the month.
- Occurs so many weeks from the start of the month. For example, every 2 months on the 2nd Sunday of the month.
- Occurs so many weeks from the end of the month. For example, every 2 months on the last Thursday of the month.
If a repeated event falls on a day not included in a particular month, the event is skipped for that month.
Yearly
This event happens once each year. In the advanced options the user is able to specify how many years apart each repeating event will occur.
It is possible to access occurrences of events from other applications using the QDL service interface. When activated the Calender application runs and displays the occurrence of the event.
QDL links are embedded into the notes of an event. When in the Detailed View,
clicking on a QDL link activates the link's application.
It is possible to set an event to repeat over a specified period of time.
| Copyright © 2009 Nokia |
Trademarks |
Qt Extended 4.4.3 |
