0.6 Calendar Service

This project tracks calendar related support (at least for the 0.6 release). This includes iCalendar import/export, recurrence, and timezone infrastructure support in the app.

People

• JeffreyHarris -- recurrence, iCalendar import/export
• AlecFlett -- calendar ui, recurrence
• GrantBaillie -- timezone
• BryanStearns -- detail view
• AndiVajda -- pyICU (datetime, timezone, calendar i18n support)
• BrianKirsch -- i18n

0.6 Specs

UI Specs (tasks are tracked in bugzilla)

• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/Detailview-0.6.htm
• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/Calendar-0.6.htm

Infrastructure specs

• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/Reccurence-0.6.html
• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/iCalendar-0.6.html
• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/Timezone-0.6.html

Additional references

• CalendarRecurrence
• ICalendarInteroperationProject
• InternationalizationProject

Status

Grant, Sheila and Alec met to discuss proposals for staging some of the recurrence and timezone features over M5 and M6. We also noted some of the major dependencies. In summary, we have decided to try and complete the recurrence features first and have the timezone functionality come in a bit later.

Recurrence

We can look at staging the recurrence feature as follows:

• 1. Import an iCalendar file with recurring events and have them display in the calendar view.
  • It would be nice to have this for the checkpoint an Aug 1st.
  • Jeffrey will have to change 5-6 lines of code to make this work. We think that it's benefitial to go ahead and try and do this.
• 2. Repeating events show up in the detail view - mapped to chandler recurrence or with custom recurrence. The detail view fields would not be editable.
  • Alec thinks we can target this for the checkpoint an Aug 8th.
• 3. Support editable recurring events - creating new events and various edits.
  • A quite a few things need to come together to make this work. We estimate that we will need a couple of weeks to get this running so we are targetting M5 for this.
• 4. Testing, trying all the various modification scenarios, popup dialogs for changes etc.
  • This will likely happen after M5.

Timezones

It make sense to wait for some of the bigger recurrence checkins before we bringin the timezone features. We can stage things as follows.

• 1. Handle and display default tz when running Chandler - add the drop down in the calendar view.
  • Grant will add this in for Aug 1st milestone even if the field is disabled. Mimi can at least look at the ui and positioning etc.
  • Need to get the list of timezones for the drop-down from Mimi.
• 2. Import a calendar and have the detail view display the right timezone - don't handle edits.
  • Need Jeffrey to complete some tasks.
  • We could sort of turn on the widgets in the detail view to start this work but it wouldn't be testable.
  • We might have some of this in M5 but likely not complete enough for any formal testing.
• 3. Responding to timezone updates
  • A. Changing the global timezone - update calendar view and mini calendar busy bars.
    • Probably post M5.
    • Some busy bar dependencies.
  • B. Changing the detail view timezone - adjust the event in the calendar view.
    • Probably post M5.

0.6 Tasks