188
edits
No edit summary |
|||
| Line 7: | Line 7: | ||
==Wish List== | ==Wish List== | ||
* Inline editing an occurrence of a recurring event creates an exeption of the recurrency pattern and changes this occurrence only. | |||
* If recurring events with exceptions are changed ("All events"), the exception is not changed. This applies to times, titles, descriptions, alarms, attendees, ... | |||
* tasks | |||
** 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 | |||
--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 | |||
edits