Calendar:Feature Implementations:Error Reporting

From MozillaWiki
Revision as of 11:11, 16 April 2006 by Garyvdm (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

NOTE: This is not complete. I have just save it - cause I scared I will lose what I have done so far.

Calendar Error Reporing

This page descibes how I (garyvdm) would like to implement error reporting (ER).

Bug 323952 - need user-friendly error presentation

There are 3 places we need to cover ER:

  • When a user is adding a new calendar.
  • When a user is reloading an existing calendar.
  • When a user is publishing changes to a calendar.

Error Displayer

For all 3 areas, we will have a common piece of code to display errors. I'll call it the error displayer (ED) from now on. This will be a XBL or a XUL overlay (I'm not sure which yet.)

The ED will look similar to the Error pages in Firefox. eg: it might display the following:

CalendarErrorDisplayer.png

The ED must be able to handle the following errors:

  • Unknown protocol.
  • Unable to resolve server name.
  • Responce timeout.
  • Server returned Error code.
  • Error in the format of the calendar returned. (eg: Malformed ICS file)

Adding a new calendar

The behavior of the last page of the Create New Calendar wizzard needs to be changed. It currently adds the calender to the list of calendars immediately, and the main window attempts to load the calendar - and error are reported in a sepperate window.

How I think it should work is a follows:

  • The wizzard need to try load the calendar before it add it to the main app window. While it is trying to load the calender, it will display this: