Home · All Namespaces · All Classes · Grouped Classes · Modules · Functions

PIM: Tasks
Functional Description

The Tasks application allows the user to prioritize tasks, manage due dates and, when appropriate, mark tasks as completed.

Features

• Add Task
• Beaming
• Categories
• Data Model
• Delete Task
• Edit Task
• Filtering
• Maximum Number of Tasks
• Memory
• Priorities
• QDL Support
• Storage
• Task Views

Add Task

It is possible to add tasks. The application does not add a task without a description.

Beaming

It is possible to beam tasks to or from another device using Bluetooth, IR, and other mechanisms supported by the QtopiaSendVia mechanism.

Categories

It is possible to categorize tasks.

Data Model

A task consists of the following data:

• A single line text description.
• A priority ranging from 1 as the highest priority to 5 as the lowest priority.
• A multi-line text note.
• A status consisting of:
  • Not started
  • In Progress
  • Completed
  • Waiting
  • Deferred

• A percentage completed. Not applicable if task status is Not Started or Completed.
• The date the task is due for completion. This is optional.
• The date the task was started. Not applicable if the task status is Not Started.
• The date the task was completed. Only applicable if the task status is Completed.
• A pattern of repetition. Only applicable if the task has a due date set.
• One or more categories. If the task is not assigned any category it is marked as unfiled.

Delete Task

It is possible to delete tasks. The application prompts the user to confirm the deletion of a task.

Edit Task

It is possible to modify tasks. This includes changing the status and adding notes.

Filtering

It is possible to filter the view of tasks by category. It is possible to hide already completed tasks.

Maximum Number of Tasks

The maximum number of tasks is determined by the available device memory. Once this limit is reached it is only possible to delete tasks; they cannot be edited nor can any new tasks be added.

Memory

While running, each event requires approximately 300 bytes of storage,
plus UTF-16 string storage for the description, plus approximately 80 bytes per category membership.

Priorities

It is possible to prioritize tasks using the scale of 1 as the highest and 5 as the lowest.

QDL Support

It is possible to access tasks from other applications via the QDL service interface.
When activated the Tasks application runs and shows linked tasks.

QDL links are embedded into the notes of a task. When in the Detailed View,
clicking on a QDL link activates the link's application.

Storage

Each event requires approximately 100 bytes of storage plus UTF-8 string
storage for the description, plus approximately 16 bytes per category membership, plus approximately 50 bytes if a due date is specified.

Task Views

It is possible to view tasks in the following three ways:

• As a sorted list of tasks.
• A detailed view of a single task.
• A task opened for editing.

Sorted List

The primary display of the application shows a sorted list of tasks. In this
list a user is able to mark a task Completed (or Incomplete),
and view additional details of the task. The list of tasks displays the
description of the task, as well as brief information about the task
like status or due date.

The sorting order of the tasks is:

• Completed: incomplete tasks are shown first.
• Priority: tasks with a priority closer to 1 are shown first.
• Description: tasks are shown in alphabetic order.

From the sorted list view the user is able to:

• Create a new task through the Edit View of the task.
• View the details for the task through the Detailed View of the task.
• Mark tasks as completed or incomplete.
• Filter the list of tasks shown according to a specified category.

Detailed View

The detailed view of a task shows data for a single task. This is shown as
rich text. All the information for the task is formatted for optimum readability.

From the details view the user is able to:

• Edit the current task through the Edit View of the task.
• Delete the current task.
• Beam the current task.
• Mark the task as complete or incomplete.
• Navigate to other tasks in the sorted list in order.

Edit View

The edit view of a task allows the user to specify the data for a new task
or modify that of an existing task.

Non-applicable values are disabled or adjusted as the data changes. For example, the start date field is disabled if the the task status is marked as Not Started, and conversely, enabling the start date field will mark the task status as In Progress.

When the editing has been completed the user is able to either accept or cancel the changes they have made.