Feature #2437
Protos for Calendar interaction
Status: | Resolved | Start date: | 11/20/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Moringen | % Done: | 100% | |
Category: | Type Proposal | |||
Target version: | - |
Description
I would like to add some prototypes which are needed for communication with a calendar event providing application.
Associated revisions
Add protos for interaction with a calendaring application.
fixes #2437
- CalendarList for presenting a list of available calendars
- CalendarUpdate to publish changes in a calendar
- CalendarQuery to request calendar events in a specific time span
- CalendarQueryResult as a means to pack a set of Events and Todos with
corresponding occurrences.
Signed-off-by: Jan Moringen <jmoringe@techfak.uni-bielefeld.de>
Backport: Add protos for interaction with a calendaring application.
- CalendarList for presenting a list of available calendars
- CalendarUpdate to publish changes in a calendar
- CalendarQuery to request calendar events in a specific time span
- CalendarQueryResult as a means to pack a set of Events and Todos with
corresponding occurrences.
Signed-off-by: Jan Moringen <jmoringe@techfak.uni-bielefeld.de>
(cherry picked from commit 48115fb3cec440d6211d78e02d11c048f40fa471)
History
#1 Updated by J. Moringen over 8 years ago
- Status changed from New to In Progress
- Assignee set to J. Moringen
Reviewing …
#2 Updated by J. Moringen over 8 years ago
- File 0001-changes.patch added
I suggest the attached changes.
Questions:
- CalendarQuery [Renamed from CalendarRequest]
- Why are search_{todos,events} optional while calculate_time_periods is required?
#3 Updated by J. Moringen over 8 years ago
- Status changed from In Progress to Feedback
- Assignee changed from J. Moringen to V. Richter
#4 Updated by V. Richter over 8 years ago
J. Moringen wrote:
I suggest the attached changes.
Good.
Questions:
- CalendarQuery [Renamed from CalendarRequest]
- Why are search_{todos,events} optional while calculate_time_periods is required?
That is certainly wrong. calculate_time_periods should be optional.
#5 Updated by J. Moringen over 8 years ago
- Status changed from Feedback to In Progress
- Assignee changed from V. Richter to J. Moringen
#6 Updated by J. Moringen over 8 years ago
- % Done changed from 0 to 80
#7 Updated by Anonymous over 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Applied in changeset rst-proto|48115fb3cec440d6211d78e02d11c048f40fa471.