|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectcom.google.gdata.data.AbstractExtension
com.google.gdata.data.ExtensionPoint
com.google.gdata.data.extensions.Reminder
public class Reminder
GData schema extension describing a reminder on an event. You can represent a set of reminders where each has a (1) reminder period and (2) notification method. The method can be either "sms", "email", "alert", "none", "all".
The meaning of this set of reminders differs based on whether you are reading or writing feeds. When reading, the set of reminders returned on an event takes into account both defaults on a parent recurring event (when applicable) as well as the user's defaults on calendar. If there are no gd:reminders returned that means the event has absolutely no reminders. "none" or "all" will not apply in this case.
Writing is different because we have to be backwards-compatible (see *) with the old way of setting reminders. For easier analysis we describe all the behaviors defined in the table below. (Notice we only include cases for minutes, as the other cases specified in terms of days/hours/absoluteTime can be converted to this case.)
Notice method is case-sensitive: must be in lowercase!
no method method method= or method=all =none email|sms|alert ____________________________________________________________________________ no gd:rem *no reminder N/A N/A 1 gd:rem *use user's no reminder InvalidEntryException def. settings 1 gd:rem min=0 *use user's no reminder InvalidEntryException def. settings 1 gd:rem min=-1 *no reminder no reminder InvalidEntryException 1 gd:rem min=+n *override with no reminder set exactly one reminder +n for user's on event at +n with given selected method methods multiple gd:rem InvalidEntry- InvalidEntry- copy this set exactly Exception ExceptionHence, to override an event with a set of reminder