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.
- Date and Time Picker Controls API
- IAppointment interface
- IContact interface
- IPOutlookApp2 interface
- IPOutlookApp interface
- IPOutlookItemCollection interface
- List-View Controls Reference API
Source File Listing
Contains the entry point and the main dialog window proc, as well as a number of utility functions.
Contains high-level POOM API calls for initialization, logon, and retrieving POOM properties.
Contains routines for retrieving and setting PIM Contact items. Also contains the dialog proc for creating new Contacts.
Contains routines for retrieving and setting PIM Task items. Also contains the dialog proc for creating new Tasks.
Contains routines for retrieving and setting PIM Appointment items. Also contains the dialog proc for creating new Appointments.
Contains function prototypes and global data.
Contains the resource script for dialogs and menus.
To run the code sample
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.
Build the solution (Ctrl+Shift+B).
Deploy the solution (F5).
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.
SDK: Windows Mobile 6 Professional SDK and Windows Mobile 6 Standard SDK
Development Environment: Visual Studio 2005.
ActiveSync: Version 4.5.