POOM Master

Windows Mobile SupportedWindows Embedded CE Not Supported

8/28/2008

This code sample is named PoomMaster. It demonstrates the use of the Pocket Outlook Object Model (POOM) API. The application displays currently stored PIM items (contacts, tasks, and calendar appointments) using an Owner-Drawn List-view Control. There is also functionality to create new PIM items using the IItem interface.

Feature Area

Relevant APIs

Source File Listing

  • PoomMaster.cpp
    Contains the entry point and the main dialog window proc, as well as a number of utility functions.
  • PoomData.cpp
    Contains high-level POOM API calls for initialization, logon, and retrieving POOM properties.
  • PoomContacts.cpp
    Contains routines for retrieving and setting PIM Contact items. Also contains the dialog proc for creating new Contacts.
  • PoomTasks.cpp
    Contains routines for retrieving and setting PIM Task items. Also contains the dialog proc for creating new Tasks.
  • PoomCalendar.cpp
    Contains routines for retrieving and setting PIM Appointment items. Also contains the dialog proc for creating new Appointments.
  • PoomMaster.h
    Contains function prototypes and global data.
  • PoomMaster.rc
    Contains the resource script for dialogs and menus.

Usage

To run the code sample

  1. Navigate to the solution file (*.sln), and double-click it. By default, the solution files are copied to the following folders:

    C:\Program Files\Windows Mobile 6 SDK\Samples\Common\CPP\Win32\PoomMaster

    Microsoft Visual Studio 2005 launches and loads the solution.

  2. Build the solution (Ctrl+Shift+B).

  3. Deploy the solution (F5).

Remarks

For the sake of simplicity, only a few properties for each item are shown — typically the subject and one or two other essential values (such as a phone number for contact, or a date and time for an appointment).

Functionally, PoomMaster has three modes of display, each accessible from the Modes menu: Tasks, Contacts, or Appointments (labeled as Calendar in the menu). New items corresponding to the current mode can be created from each display using New Item from the Options menu. The Options menu also contains a Quit item. This is for the user's convenience, and is not demonstrative of typical Windows Mobile application behavior.

Development Environments

SDK: Windows Mobile 6 Professional SDK and Windows Mobile 6 Standard SDK 

Development Environment: Visual Studio 2005.

ActiveSync: Version 4.5.

See Also

Concepts

Code Samples for Windows Mobile

Other Resources

Pocket Outlook Object Model (POOM)