This section lists the implementation specifics of the Personal Information Management API at package level.
The javax.microedition.pim
package contains
PIM API classes and interfaces.
The PIMList.getFieldLabel()
, PIMList.getAttributeLabel()
, and PIMList.getArrayElementLabel()
methods
should be used for obtaining localized labels for fields, attributes,
and string array elements.
In the Symbian implementation, the PIM.listPIMLists(PIM.EVENT_LIST)
method returns the supported EventList
names in the following order:
Meeting
Memo
Anniversary
The exact names returned by the method are localized and can also depend on the platform.
The following table describes the PIMLists
supported by the Symbian platform.
List name |
Class |
Corresponding PIM data |
---|---|---|
Contacts |
|
Phonebook entries |
Meeting |
|
Calendar meeting entries |
Memo |
|
Calendar memo entries Note: From Symbian^3 onwards, the native calendar database no longer supports memo entries. |
Anniversary |
|
Calendar anniversary entries |
To-do notes |
|
To-do note entries |
The list names depend on the used localization variant. For more information, see the section Runtime environment notes.
The Contact
, Event
, and ToDo
item objects in lists are persistent so that they are read from
the database during list initialization. After this, external changes
are applied to the items so that there is no need to reread entire
lists.
The items are refreshed from a native database whenever
any of the PIMList.items
variations is called.
Note: Although the PIM API does not constitute any explicit UI components, the implementation shows an extra confirmation dialog for item and category deletion operations. In the Series 40 implementation, these confirmation dialogs are suppressed when the API is used from the Manufacturer security domain.
In
the Series 40 implementation, the PIM.listPIMLists(PIM.EVENT_LIST)
method returns the supported EventList
names
in the following order:
Meeting
Call
Birthday
Memo
Reminder
The exact names returned by the method are localized and can also depend on the platform.
The following table describes the PIMLists
supported by the Series 40 platform.
List name |
Class |
Corresponding PIM data |
---|---|---|
Contacts |
|
Phonebook entries in device memory |
Contacts |
|
Phonebook entries in SIM |
Meeting |
|
Calendar meeting entries |
Call |
|
Calendar call entries |
Birthday |
|
Calendar birthday entries |
Memo |
|
Calendar memo entries |
Reminder |
|
Calendar reminder entries |
ToDo |
|
To-do note entries |
The Contact
, Event
, and ToDo
item objects in lists are persistent
so that they are read from the database during list initialization.
After this, external changes are applied to the items so that there
is no need to reread entire lists. The items are refreshed from a
native database whenever any of the PIMList.items
variations is called.