Changes for page Calendar Application
Last modified by Ecaterina Valica on 2014/01/15 13:50
From version 11.6
edited by Silvia Rusu
on 2011/06/20 14:17
on 2011/06/20 14:17
Change comment:
There is no comment for this version
To version 13.2
edited by Vlad Merticariu
on 2011/06/22 10:59
on 2011/06/22 10:59
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SilviaRusu1 +XWiki.vladm - Content
-
... ... @@ -44,12 +44,12 @@ 44 44 Each calendar will be stored in a space. A space can only contain one calendar. Each event must be stored in its own document and should have: 45 45 46 46 * **Name** 47 -* **Date**: User should be able to mark an event as **recurring**. Similarly to Google Calendar, event recurrence should be customizable47 +* **Date**: User should be able to mark an event as **recurring**. 48 48 * **Location**: Link to Google Maps 49 49 * **Description** 50 50 * **Category** 51 51 * **Color**: The event will have a default color and event creators may select a different color for the new event from a given list 52 -* **Notifications**: Email notifications may be sent to the event creator and the users he selects **n**minutes/hours/days/weeksbeforethe event (n = a number the event creator fills in; minutes/hours/days/weeks are options in a drop-down).The event creator can also choose to be notified via RSS about event changes.52 +* **Notifications**: Email notifications may be sent to the event creator and the users he selects (10 minutes, 30 minutes, 1 hour, 1 day, 1 week) The event creator can also choose to be notified via RSS about event changes. 53 53 * **Privacy options**: Default, Private, Public 54 54 * The possibility to **add guests**. Guests can appear in the form of wiki users or email addresses. Suggestions should be available if the event creator starts typing in a user's name. Guests will be notified by email they have been invited to the event and they should be able to RSVP (confirm their presence) via email 55 55 * **Set rights for guests**. The event creator can grant users one, some or all of the following rights: modify the event, invite other guests to the event, see the guest list ... ... @@ -110,6 +110,11 @@ 110 110 * **Description** 111 111 * **Location** 112 112 113 + 114 +* Week starts on Sunday/Monday/Saturday 115 +* Show events you have declined: Yes/No 116 +* Automatically add invitations to my calendar: Yes/No 117 + 113 113 === Privacy === 114 114 115 115 **Privacy settings for calendar** ... ... @@ -141,10 +141,12 @@ 141 141 * Comments being added 142 142 ))) 143 143 144 -In addition, **reminders** can be **sent by default to the calendar owner** via email **n**minutes/hours/days/weeksbeforethe event (n = a number the calendar owner fills in; minutes/hours/days/weeks are options in a drop-down).149 +In addition, **reminders** can be **sent by default to the calendar owner** via email: 10 minutes, 30 minutes, 1 hour, 1 day, 1 week 145 145 146 -== =DatendLanguage===151 +== Search == 147 147 153 +The "View event list" livetable can be used to filter events by date, location, and even to do searches within the event descriptions. 154 + 148 148 == Suggestions == 149 149 150 150 * Ability to print calendar ... ... @@ -153,6 +153,14 @@ 153 153 * Notifications by SMS could be interesting 154 154 * Gadget integration 155 155 163 +==Further work== 164 + 165 +* Select language? 166 +* Select from different time zones? 167 +* Select date format? 168 +* Select time format? 169 +* Similarly to Google Calendar, event recurrence should be customizable 170 + 156 156 = Technicalities = 157 157 158 158 The event-calendar part of the application will be implemented in the following way: ... ... @@ -163,15 +163,19 @@ 163 163 164 164 Event class properties: 165 165 166 -* title (Title: text): // the title of the event// 167 -* description (Description: text): // a short description of the event// 168 -* location (Location: text): // the location where the event will take place// 181 +* name (Name: text): // the title of the event// 169 169 * startDate (Start date: date(dd/MM/yyy)): // the date when the event starts// 170 170 * startTime (Start time: static list): // the hour when the event starts// 171 171 * endDate (End date: date(dd/MM/yyyy)): // the date when the event ends// 172 172 * endTime (End time: static list): //the hour when the event ends// 186 +* allDay (All day: bool): //checkbox which indicates that startTime is 00:00 of the startDate and endTime is 00:00 of the day after endDate 187 +* repeats (Repeats: static list (daily, weekly, monthly, yearly)): // how often the event repeats // 188 +* repeatsUntil (Until: date(dd/MM/yyyy)): // the date when the recursion of the event ends// 189 +* description (Description: text): // a short description of the event// 190 +* location (Location: text): // the location where the event will take place// 173 173 * category(Category: database list): // the category of the event// 174 -* privacySettings(Privacy: static list): // set the event to be public (visible to everyone) or private (visible only to the user)// 192 +* color(Color: static list): // the color of the event// 193 +* privacy(Privacy: static list): // set the event to be default, public (visible to everyone) or private (visible only to the user)// 175 175 * notifications(notifications: bool): // indicates if the notifications are activated or not// 176 176 * userNotifiationList(Users to receive notifications: ?): // the list of users to be notified about the event// 177 177 ... ... @@ -195,3 +195,5 @@ 195 195 196 196 * title(Title: text): // the title of the category// 197 197 * description(Description: text): // a short description of the category// 217 + 218 +