Introduction to Calendar Store Programming Guide

Explains how to access iCal data.

Who Should Read This Document?

You should read this document if you want to display or edit iCal data in your application. Calendar Store is ideal for integrating subsets of iCal data into your application. Calendar Store simplifies fetching and saving changes to records since you don’t have to implement your own persistent storage or deal with the complexity of the Calendars schema. Calendar Store also notifies applications of changes made in iCal so your application data stays fresh. It is suitable for developing widgets, plug-ins, and augmenting other types of applications that use calendar data. It is not suitable for implementing full-featured calendar applications.

Note: Calendar Store does not provide complete read/write database access to all iCal records.

Concurrency Note: The Calendar Store framework is thread safe. No additional locking or other synchronization is required. The framework handles synchronization for you.

Organization of This Document

You should read these articles if you just want to fetch Calendar Store objects:

Calendar Store Overview describes the Calendar Store architecture and core classes.

Fetching Objects explains how to fetch calendar, event, and task objects.

Observing Changes explains how to observe changes made to these objects by other processes.

You should also read these articles if you want to create or modify Calendar Store objects:

Creating Objects explains how to create commonly used objects: calendars, events, tasks, and alarms.

Creating Recurring Events explains how to create recurring events—events that repeat according to a custom pattern.

Saving Changes explains how to save changes you make locally to Calendar Store objects.

Introduction to Calendar Store Programming Guide

Who Should Read This Document?

Organization of This Document

See Also