Abstract: Methods, program products, and systems for location-based reminders are disclosed. A first user device can receive an input specifying that a reminder be presented at a given location. The first user device can provide a reminder request, including type and content of the reminder and the location, to a server computer for pushing to one or more user devices. A second user device, upon receiving the reminder request, can determine a device location of the second user device. If the given location matches the device location, the second user device can present the reminder in a user interface.

Abstract: Some embodiments provide a calendar application for associating travel times with appointments in a calendar. For an appointment in a calendar, the calendar application creates a representation of the travel time to display in the calendar layout. The calendar application provides a travel time tool to create the travel time representation for an appointment. The travel time representation is an item in the calendar UI just like an appointment is an item in the calendar UI. The travel time item represents the estimated time required to travel between a particular location and the location of the appointment.

Abstract: Methods, systems, and graphical user interfaces are provided for showing calendar events that are not visible on screen. Event objects are shown when an event is within a viewable time range, but the event object is partially drawn on screen (e.g. clipped) when the event is not within a viewable time range. The displayed parts of event objects indicating off-screen event can stack on top of each other to provide information about a number of off-screen events for a particular day. With the events clipped and stacked, a user has a visual indicator that there are events off screen for a particular day. As a user scrolls to the time of the event, the event can completely reveals itself.

Abstract: Methods, systems, and graphical user interfaces are provided for showing calendar events that are not visible on screen. Event objects are shown when an event is within a viewable time range, but the event object is partially drawn on screen (e.g. clipped) when the event is not within a viewable time range. The displayed parts of event objects indicating off-screen event can stack on top of each other to provide information about a number of off-screen events for a particular day. With the events clipped and stacked, a user has a visual indicator that there are events off screen for a particular day. As a user scrolls to the time of the event, the event can completely reveals itself.

Abstract: The calendaring techniques and interfaces described herein provide access to calendar data stored in a server hosted calendar store to applications. The calendar data includes calendar events and tasks. In one aspect, an application program interface (API) retrieves an occurrence from a series of reoccurring calendar data upon request from an application. In another aspect, the API sends calendar data provided by the application to a server program that manages a calendar store for storage and queries the server program to retrieve calendar data requested by the application from the calendar store. In yet another aspect, the API sends notifications that the calendar store has changed to interested applications.

Abstract: A text input is received in a calendar context. The text input is processed with a context-neutral extraction process to generate a first set of elements and with a calendar-specific extraction process to generate a second set of elements. A calendar event is created from the first set of elements and the second set of elements and displayed on a display device without confirming the elements of the calendar event with a user.

Abstract: Methods, systems, and computer-readable media for scheduling a recurring event are disclosed. When a calendar application receives an invitation from an organizer to an invite, the calendar application expands the recurring event into a plurality of occurrences, and detects any scheduling conflicts that can be caused by each of the plurality of occurrences. The calendar application notifies the invitee of the detected scheduling conflicts before the invitee makes a decision regarding the invitation. An invitee is provided an opportunity to accept only the non-conflicting occurrences of the recurring event. If the invitee chooses to accept only the non-conflicting occurrences, the invitee is given opportunities to respond to each of the conflicting occurrences separately. The organizer is notified of the invitee's responses regarding the non-conflicting occurrences and the conflicting occurrences.

Abstract: The calendaring techniques and interfaces described herein provide access to calendar data stored in a server hosted calendar store to applications. The calendar data includes calendar events and tasks. In one aspect, an application program interface (API) retrieves an occurrence from a series of reoccurring calendar data upon request from an application. In another aspect, the API sends calendar data provided by the application to a server program that manages a calendar store for storage and queries the server program to retrieve calendar data requested by the application from the calendar store. In yet another aspect, the API sends notifications that the calendar store has changed to interested applications.

Abstract: The calendaring techniques and systems described herein enable a user to more easily resolve conflicts for attendees to an event by visually indicating available time slots for all attendees in a calendar window or in a timeline window separate from the calendar window. The first available time slot may be automatically selected or the user may select an available slot to reschedule the event. In another aspect, inspector windows are displayed within a calendar window to show summary or details for an event. An inspector window can also be displayed when a change to an event is detected. In yet another aspect, calendars for multiple accounts accessible by a user are merged into a single calendar view.

Abstract: A meeting originator associates a file with a meeting event by dropping the file on a meeting event window displayed within a calendar window. The file is copied to a directory on the originator's computer and a meeting invitation is created containing a directory path to a corresponding directory on a server that stores a copy of the file. The meeting invitation is sent to the server for distribution to attendees of the meeting, who access the file from the server. The originator also indicates permissions on the server directory for the attendees. The file may be modified by the originator, or by an attendee having appropriate permissions, by dropping a modified version on the meeting event window. The server notifies the attendees and/or the originator that the meeting event has changed.