Changes for page Calendar Application

Last modified by Ecaterina Valica on 2014/01/15 13:50

From version 13.4
edited by Vlad Merticariu
on 2011/06/22 11:12
Change comment: There is no comment for this version
To version 14.2
edited by Ecaterina Valica
on 2011/06/22 13:59
Change comment: Added comment

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.vladm
1 +XWiki.evalica
Content
... ... @@ -17,7 +17,7 @@
17 17  * Import/export: // tbd - ical feeds //
18 18  * Microformats support: // tbd//
19 19  * JS drag & drop on the calendar table for changing the dates/hours of the events ?: // an event can be dragged from one slot of the calendar table to another slot//
20 -* RSS notifications: // tbd//
20 +* RSS notifications: // a document to generate RSS feed will be created//
21 21  * Email notifications: // emails with information about the event are sent to the calendar creator and to the selected users (when?)//
22 22  * Privacy settings on events: // events can be public or private, public events are visible to everyone, private events are visible only to the calendar creator//
23 23  * Privacy settings on calendar
... ... @@ -30,7 +30,7 @@
30 30  * Daily view of the calendar, listing all the events in that day
31 31  * Have an API for accessing events
32 32  * Each event must be stored in its own document
33 -* Have different calendars for each space
33 +* Each calendar is stored in its own space (only 1 calendar/space)
34 34  
35 35  = Detailed Functionality =
36 36  
... ... @@ -49,7 +49,7 @@
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 (10 minutes, 30 minutes, 1 hour, 1 day, 1 week) 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)
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
... ... @@ -111,7 +111,7 @@
111 111  * **Location**
112 112  
113 113  
114 -* Week starts on Sunday/Monday/Saturday
114 +* Week starts on Sunday/Monday/Saturday ? //should this be done automatically depending on the user's location?//
115 115  * Show events you have declined: Yes/No
116 116  * Automatically add invitations to my calendar: Yes/No
117 117  
... ... @@ -188,21 +188,25 @@
188 188  * repeatsUntil (Until: date(dd/MM/yyyy)): // the date when the recursion of the event ends//
189 189  * description (Description: text): // a short description of the event//
190 190  * location (Location: text): // the location where the event will take place//
191 -* category(Category: database list): // the category of the event//
192 -* color(Color: static list): // the color of the event//
191 +* category (Category: database list): // the category of the event//
192 +* color (Color: static list): // the color of the event//
193 193  * privacy(Privacy: static list): // set the event to be default, public (visible to everyone) or private (visible only to the user)//
194 -* emailNotifications(Email Notifications: static list): // indicates when the reminders for the event should be sent to the creator and to the guest list//
195 -* rssNotifications(RSS Notification: bool): // indicates if the creator should receive RSS notifications //
196 -* guestList(Guest List: user list): // the list of users invited to the event, waiting for confirmation//
197 -* confirmedGuests(Attending guests: user list, disabled): // the list of users who have confirmed their attendance to the event//
198 -* declinedGuests(Non-attending guests: user list, disabled): // the list of users who have declined their attendance to the event//
194 +* emailNotifications (Email Notifications: static list): // indicates when the reminders for the event should be sent to the creator and to the guest list//
195 +* guestList (Guest List: user list): // the list of users invited to the event, waiting for confirmation//
196 +* confirmedGuests (Attending guests: user list, disabled): // the list of users who have confirmed their attendance to the event//
197 +* declinedGuests (Non-attending guests: user list, disabled): // the list of users who have declined their attendance to the event//
198 +* guestRights (Guests can: static lists): // Indicates if the guests can Modify event, Invite other guests, View guest list //
199 199  
200 200  Calendar class properties:
201 201  
202 -* title (Title: text): // the title of the calendar//
202 +* name (Name: text): // the name of the calendar//
203 203  * description(Description: text): // a short description of the calendar//
204 -* privacySettings(Privacy: static list): // set the calendar to be public(visible to everyone) or private(visisble only to the user)//
204 +* privacy(Privacy: static list): // set the calendar to be public(visible to everyone), visible to specific users or private(visisble only to the user)//
205 +* shareList(Share calendar: user list): // if privacy is set to visible for specific users, this list will contain the users who can view it//
205 205  * owner(Owner: user): // the user who owns the calendar//
207 +* weekStart(Week starts on: static list): // The day when the week starts (Sunday, Monday or Saturday) ? should this be done automatically depending on the user's location?//
208 +* showDeclinedEvents(Show Events you have declined: bool): // Indicates if events which have been declined should be added to the calendar//
209 +* addInvitations(Automatically add invitations to the calendar: bool): // Indicates if the events to which the user has been invited should be added to the calendar//
206 206  
207 207  Calendar class sheets:
208 208  
... ... @@ -209,8 +209,8 @@
209 209  * CalendarViewDaySheet: // contains the display of the calendar table in "day" view//
210 210  * CalendarViewWeekSheet: // contains the display of the calendar table in "week" view//
211 211  * CalendarViewMonthSheet: // contains the display of the calendar table in "month" view//
212 -* CalendarViewYearSheet?
213 -* CalendarFormSheet: // contains the form for adding new events//
216 +* CalendarViewYearSheet: // contains the display of the calendar table in "year" view//
217 +* CreateCalendarEvent: // contains the form for adding new events//
214 214  * CalendarEventListSheet: // contains the list of events for the specific calendar, with edit and delete links if the user has editing rights//
215 215  
216 216  Category class properties:
XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,3 @@
1 +I don't think we will need a livetable to list all the events since you can see/delete/edit all events in the year/month/week views. The calendar events are much powerful when they are in a timeline than seeing them in a list.
2 +
3 +Also I don't think is necessary the concept of categories when you can have multiple calendars. Right now in Google Calendar you can create multiple calendars and attribute each calendar a goal (have a personal one, a xwiki one, a birthday, etc). In this use case the concept of categories is replaced by multiple calendars.
Date
... ... @@ -1,0 +1,1 @@
1 +2011-06-22 11:59:17.410