Calendar:QA Feature Specification: Difference between revisions

Calendar:QA Feature Specification (view source)

Revision as of 20:08, 25 October 2006

1,049 bytes removed , 25 October 2006

→‎Wish List

Sebo

188

edits

@@ Line 7: / Line 7: @@
 ==Wish List==
-*recurrencies
-** Inline editing an occurrence of a recurring event creates an exeption of the recurrency pattern and changes this occurrence only.
+* editing recurring events
-** If recurring events with exceptions are changed ("All events"), the exception is not changed. This applies to times, titles, descriptions, alarms, attendees, ...
+* copy/paste recurring events
-** copy/paste recurring events ...
-** hitting del after selecting one occurrence
-** hitting del after selecting all occurrences of an recurring event
 * tasks
 ** there is a [[Calendar:Task Support|Feature Specification for Tasks]]. I'm not sure if this has been agreed on. It does not show the actual behaviour, though.
-** can have start date/can have due date/(can have duration?)
-** are shown in main view if option("Tasks in View") is set
-** are shown in main view from start date until due date OR
-** are shown in main view from start date until [start date + duration] OR
-** are shown in main view from [due date - duration] until due date
-** can have alarms relative to start date/relative to due date/relative to [due date - duration]
-** tasks can be converted to events in the dialog
 * email invitations
-** should updated email invitations overwrite existing entries in the calendar?
+** see [[Calendar:Feature_Implementations:iTIP-iMIP:Current_iTIP_Design]]
 * printing
 ** a weekly view, similar to the weekly view provided in the google calendar
 ** generate pdf-files as result of a print preview (see google calendar)
---Please correct the above if I am mistaken. I am aware that task semantics are currently discussed in the newsgroup. I just put down some possible solutions. --Sebo