Skip to Content

Changes for page Calendar Application

Last modified by Ecaterina Valica on 2014/01/15 13:50
From version 19.5
edited by Silvia Rusu
on 2011/06/22 20:52
Change comment: There is no comment for this version
To version 15.1
edited by Vlad Merticariu
on 2011/06/22 14:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SilviaRusu
1 +XWiki.vladm
Content
... ... @@ -32,21 +32,6 @@
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 50  = Detailed Functionality =
51 51  
52 52  == Adding events ==
... ... @@ -62,7 +62,7 @@
62 62  * **Date**: User should be able to mark an event as **recurring**.
63 63  * **Location**: Link to Google Maps
64 64  * **Description**
65 -* **Category** (e.g. Personal, Work)
50 +* **Category** : //? Do we need this once a user can have multiple calendars? //
66 66  * **Color**: The event will have a default color and event creators may select a different color for the new event from a given list
67 67  * **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)
68 68  * **Privacy options**: Default, Private, Public
... ... @@ -125,6 +125,7 @@
125 125  * **Description**
126 126  * **Location**
127 127  
113 +
128 128  * Week starts on Sunday/Monday/Saturday ? //should this be done automatically depending on the user's location?//
129 129  * Show events you have declined: Yes/No
130 130  * Automatically add invitations to my calendar: Yes/No
... ... @@ -138,13 +138,6 @@
138 138  * Visible for specific wiki users -> Share calendar
139 139  * Private
140 140  
141 -**Privacy settings for the categories**
142 -Each category can be:
143 -
144 -* Public
145 -* Visible for specific wiki users -> Share category
146 -* Private
147 -
148 148  **Default privacy settings for events**
149 149  Events can be
150 150  
... ... @@ -181,7 +181,7 @@
181 181  * Notifications by SMS could be interesting
182 182  * Gadget integration
183 183  
184 -== Further work ==
163 +==Further work==
185 185  
186 186  * Select language?
187 187  * Select from different time zones?
... ... @@ -204,7 +204,7 @@
204 204  * startTime (Start time: static list): // the hour when the event starts//
205 205  * endDate (End date: date(dd/MM/yyyy)): // the date when the event ends//
206 206  * endTime (End time: static list): //the hour when the event ends//
207 -* 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//
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
208 208  * repeats (Repeats: static list (daily, weekly, monthly, yearly)): // how often the event repeats //
209 209  * repeatsUntil (Until: date(dd/MM/yyyy)): // the date when the recursion of the event ends//
210 210  * description (Description: text): // a short description of the event//
... ... @@ -242,3 +242,5 @@
242 242  
243 243  * title(Title: text): // the title of the category//
244 244  * description(Description: text): // a short description of the category//
224 +
225 +
actions.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.evalica
Size
... ... @@ -1,1 +1,0 @@
1 -70.2 KB
Content
addMenu.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.evalica
Size
... ... @@ -1,1 +1,0 @@
1 -18.1 KB
Content
eventFields.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.evalica
Size
... ... @@ -1,1 +1,0 @@
1 -73.9 KB
Content
monthView.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.evalica
Size
... ... @@ -1,1 +1,0 @@
1 -87.5 KB
Content
weekView.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.evalica
Size
... ... @@ -1,1 +1,0 @@
1 -62.2 KB
Content
yearView.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.evalica
Size
... ... @@ -1,1 +1,0 @@
1 -75.8 KB
Content
XWiki.XWikiComments[1]
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.Enygma
Comment
... ... @@ -1,7 +1,0 @@
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,1 +1,0 @@
1 -2011-06-22 12:35:20.0
Reply To
... ... @@ -1,1 +1,0 @@
1 -0