Skip to Content

Changes for page Calendar Application

Last modified by Ecaterina Valica on 2014/01/15 13:50
From version 15.1
edited by Vlad Merticariu
on 2011/06/22 14:22
Change comment: There is no comment for this version
To version 20.2
edited by Vlad Merticariu
on 2011/07/06 16:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,6 +32,26 @@
32 32  * Each event must be stored in its own document
33 33  * Each calendar is stored in its own space (only 1 calendar/space)
34 34  
35 += Alternatives =
36 +
37 +**Calendar aggregator**
38 +
39 +The WebHome of the application is an aggregated calendar which displays the events from all the calendars of a user.
40 +The user creates several calendars (e.g. Personal, Work) which can be visualized both individually and together, on the main page of the application.
41 +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).
42 +
43 +
44 +**Individual calendars with categories**
45 +
46 +The users creates calendars which are individual entities and each event is assigned a category when added.
47 +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.
48 +The current technicalities are meant for this alternative.
49 +
50 +**Unique calendar/user**
51 +
52 +Every user has only one calendar. Events can be categorized just as above.
53 +For sharing the user has 2 options: share the entire calendar or share a category, which, as functionality, makes it similar to the Calendar aggregator alternative.
54 +
35 35  = Detailed Functionality =
36 36  
37 37  == Adding events ==
... ... @@ -47,7 +47,7 @@
47 47  * **Date**: User should be able to mark an event as **recurring**.
48 48  * **Location**: Link to Google Maps
49 49  * **Description**
50 -* **Category** : //? Do we need this once a user can have multiple calendars? //
70 +* **Category** (e.g. Personal, Work)
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 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
... ... @@ -110,7 +110,6 @@
110 110  * **Description**
111 111  * **Location**
112 112  
113 -
114 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
... ... @@ -124,6 +124,13 @@
124 124  * Visible for specific wiki users -> Share calendar
125 125  * Private
126 126  
146 +**Privacy settings for the categories**
147 +Each category can be:
148 +
149 +* Public
150 +* Visible for specific wiki users -> Share category
151 +* Private
152 +
127 127  **Default privacy settings for events**
128 128  Events can be
129 129  
... ... @@ -160,7 +160,7 @@
160 160  * Notifications by SMS could be interesting
161 161  * Gadget integration
162 162  
163 -==Further work==
189 +== Further work ==
164 164  
165 165  * Select language?
166 166  * Select from different time zones?
... ... @@ -183,7 +183,7 @@
183 183  * startTime (Start time: static list): // the hour when the event starts//
184 184  * endDate (End date: date(dd/MM/yyyy)): // the date when the event ends//
185 185  * 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
212 +* 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 187  * repeats (Repeats: static list (daily, weekly, monthly, yearly)): // how often the event repeats //
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//
... ... @@ -192,10 +192,11 @@
192 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 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 //
221 +* guestViewList (Guest View List: database list): // the list of users invited to the event, having view rights, waiting for confirmation//
222 +* guestEditList (Guest Edit List: database list): // the list of users invited to the event, having edit rights, waiting for confirmation//
223 +* attendingGuests (Attending guests: database list): // the list of users who have confirmed their attendance to the event//
224 +* nonattendingGuests (Non-attending guests: database list): // the list of users who have declined their attendance to the event//
225 +* notifiedGuests (Notified Guests: database list): // the list of guests who have received notifications about their event invitation //
199 199  
200 200  Calendar class properties:
201 201  
... ... @@ -221,5 +221,3 @@
221 221  
222 222  * title(Title: text): // the title of the category//
223 223  * description(Description: text): // a short description of the category//
224 -
225 -
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[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