Skip to Content

Changes for page Calendar Application

Last modified by Ecaterina Valica on 2014/01/15 13:50
From version 13.1
edited by Vlad Merticariu
on 2011/06/22 09:52
Change comment: There is no comment for this version
To version 17.1
edited by Vlad Merticariu
on 2011/06/22 15:36
Change comment: There is no comment for this version

Summary

Details

Page properties
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  
... ... @@ -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 customizable
47 +* **Date**: User should be able to mark an event as **recurring**.
48 48  * **Location**: Link to Google Maps
49 49  * **Description**
50 -* **Category**
50 +* **Category** : //? Do we need this once a user can have multiple calendars? //
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/weeks before the 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)
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
... ... @@ -99,7 +99,7 @@
99 99  
100 100  * **Viewing events you are invited to in your calendar**: Calendar owners will have view right by default for their own calendar (space). View rights should also be granted for events he is invited to. This means having view rights on event pages that are located in other calendars (spaces). Other rights, such as edit and comment can also be granted, depending on the settings established by the the owner when creating the event.
101 101  
102 -**View event list:** A page (modal window) with the list of all the events in the calendar is displayed, using LiveTable, were the user can filter and edit/delete events (if he has the right to do it, additional view to administrate events)
102 +**View event list:** A page (modal window) with the list of all the events in the calendar is displayed, using LiveTable, were the user can filter and edit/delete events (if he has the right to do it, additional view to administrate events) // ? Do we need this once the events can be viewed in calendar table? //
103 103  
104 104  == Settings ==
105 105  
... ... @@ -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  
... ... @@ -166,7 +166,22 @@
166 166  * Select from different time zones?
167 167  * Select date format?
168 168  * Select time format?
169 +* Similarly to Google Calendar, event recurrence should be customizable
169 169  
171 += Alternatives =
172 +
173 +**Calendar aggregator**
174 +
175 +The WebHome of the application is an aggregated calendar which displays the events from all the calendars of a user.
176 +The user creates several calendars (e.g. Personal, Work) which can be visualized both individually and together, on the main page of the application.
177 +This is very similar to Google Calendar, following the same approach. The main advantage of this is the ease of interaction between users' calendars (e.g. sharing a calendar with another user means displaying the specific calendar among his own calendars, inside the WebHome).
178 +
179 +
180 +**Individual calendars with categories**
181 +
182 +The users creates calendars which are individual entities and each event is assigned a category when added.
183 +When the user is invited to other events he can choose to view those events in one or more of his calendars while when another user shares a calendar with him he can only view that calendar, on a separate page.
184 +
170 170  = Technicalities =
171 171  
172 172  The event-calendar part of the application will be implemented in the following way:
... ... @@ -177,24 +177,35 @@
177 177  
178 178  Event class properties:
179 179  
180 -* title (Title: text): // the title of the event//
181 -* description (Description: text): // a short description of the event//
182 -* location (Location: text): // the location where the event will take place//
195 +* name (Name: text): // the title of the event//
183 183  * startDate (Start date: date(dd/MM/yyy)): // the date when the event starts//
184 184  * startTime (Start time: static list): // the hour when the event starts//
185 185  * endDate (End date: date(dd/MM/yyyy)): // the date when the event ends//
186 186  * endTime (End time: static list): //the hour when the event ends//
187 -* category(Category: database list): // the category of the event//
188 -* privacySettings(Privacy: static list): // set the event to be public (visible to everyone) or private (visible only to the user)//
189 -* notifications(notifications: bool): // indicates if the notifications are activated or not//
190 -* userNotifiationList(Users to receive notifications: ?): // the list of users to be notified about the event//
200 +* 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
201 +* repeats (Repeats: static list (daily, weekly, monthly, yearly)): // how often the event repeats //
202 +* repeatsUntil (Until: date(dd/MM/yyyy)): // the date when the recursion of the event ends//
203 +* description (Description: text): // a short description of the event//
204 +* location (Location: text): // the location where the event will take place//
205 +* category (Category: database list): // the category of the event//
206 +* color (Color: static list): // the color of the event//
207 +* privacy(Privacy: static list): // set the event to be default, public (visible to everyone) or private (visible only to the user)//
208 +* emailNotifications (Email Notifications: static list): // indicates when the reminders for the event should be sent to the creator and to the guest list//
209 +* guestList (Guest List: user list): // the list of users invited to the event, waiting for confirmation//
210 +* confirmedGuests (Attending guests: user list, disabled): // the list of users who have confirmed their attendance to the event//
211 +* declinedGuests (Non-attending guests: user list, disabled): // the list of users who have declined their attendance to the event//
212 +* guestRights (Guests can: static lists): // Indicates if the guests can Modify event, Invite other guests, View guest list //
191 191  
192 192  Calendar class properties:
193 193  
194 -* title (Title: text): // the title of the calendar//
216 +* name (Name: text): // the name of the calendar//
195 195  * description(Description: text): // a short description of the calendar//
196 -* privacySettings(Privacy: static list): // set the calendar to be public(visible to everyone) or private(visisble only to the user)//
218 +* privacy(Privacy: static list): // set the calendar to be public(visible to everyone), visible to specific users or private(visisble only to the user)//
219 +* shareList(Share calendar: user list): // if privacy is set to visible for specific users, this list will contain the users who can view it//
197 197  * owner(Owner: user): // the user who owns the calendar//
221 +* 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?//
222 +* showDeclinedEvents(Show Events you have declined: bool): // Indicates if events which have been declined should be added to the calendar//
223 +* 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//
198 198  
199 199  Calendar class sheets:
200 200  
... ... @@ -201,8 +201,8 @@
201 201  * CalendarViewDaySheet: // contains the display of the calendar table in "day" view//
202 202  * CalendarViewWeekSheet: // contains the display of the calendar table in "week" view//
203 203  * CalendarViewMonthSheet: // contains the display of the calendar table in "month" view//
204 -* CalendarViewYearSheet?
205 -* CalendarFormSheet: // contains the form for adding new events//
230 +* CalendarViewYearSheet: // contains the display of the calendar table in "year" view//
231 +* CreateCalendarEvent: // contains the form for adding new events//
206 206  * CalendarEventListSheet: // contains the list of events for the specific calendar, with edit and delete links if the user has editing rights//
207 207  
208 208  Category class properties:
actions.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +70.2 KB
Content
addMenu.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +18.1 KB
Content
eventFields.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +73.9 KB
Content
monthView.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +87.5 KB
Content
weekView.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +62.2 KB
Content
yearView.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +75.8 KB
Content
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.0
XWiki.XWikiComments[1]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Enygma
Comment
... ... @@ -1,0 +1,7 @@
1 +I agree with this.
2 +
3 +We should have a 2 views:
4 +1. Individual calendar view, that should be available on each calendar's space WebHome
5 +2. Aggregated calendar view for all the calendars and events that are visible to the current user. This could be a new tab in the user's profile (harder for an application to extend right now) or, alternatively, in the Calendar application's space WebHome (easier and makes the Calendar application space useful).
6 +
7 +The event livetable might be useful for an 'advanced search' functionality, allowing to filter events nicely.
Date
... ... @@ -1,0 +1,1 @@
1 +2011-06-22 12:35:20.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +0