Changes for page Calendar Application

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

From version 12.1
edited by Silvia Rusu
on 2011/06/20 14:32
Change comment: There is no comment for this version
To version 9.1
edited by Silvia Rusu
on 2011/06/17 17:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,7 +41,7 @@
41 41  1. Clicking a button which opens a modal window, allowing the user to insert details and save
42 42  1. Filling in a form on the event page. The user enters all the details and, after submission, he is redirected back to the calendar in view mode
43 43  
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:
44 +Each event must be stored in its own document and should have:
45 45  
46 46  * **Name**
47 47  * **Date**: User should be able to mark an event as **recurring**. Similarly to Google Calendar, event recurrence should be customizable
... ... @@ -57,7 +57,6 @@
57 57  * **Comments**: Users have the ability to comment on an event. An icon will indicate in daily and weekly view modes that the event has comments
58 58  
59 59  **More actions:**
60 -
61 61  * **Change owner**
62 62  * **RSVP for guests**: Users who are not event owners, but see an event to which they are invited in a calendar, should be able to click the "RSVP" link and confirm their presence
63 63  * **Delete event**
... ... @@ -64,12 +64,13 @@
64 64  * **Duplicate event**: Copy an event inside the calendar
65 65  * **Copy event to a different calendar**: Copy an event from the current calendar to a different calendar
66 66  
66 +
67 67  == Viewing events ==
68 68  
69 69  **View calendar:**
70 70  
71 71  * Tabbed day, week, month, yearly view
72 -* **Year view**:
72 +* **Year view**:
73 73  ** There should be 12 cells representing the 12 different months
74 74  ** When users click on a month (e.g. //June 2011//) they should be directed to that specific month in the "Month" tab
75 75  ** When users click on a day (e.g. //1//) they should be directed to that specific day in the "Day" tab
... ... @@ -93,77 +93,23 @@
93 93  ** Events should be displayed chronologically and occupy the number of cells corresponding to the number of hours the event is scheduled to last. An alert icon should be displayed when a notification is set, an attachment icon when an attachment is present, a comment icon when comments have been added. Clicking or hovering (TBD) on the event will bring up a pop-up with more details and links to edit and delete the event
94 94  ** The current day should be highlighted with a distinct color (same as the one used for the other views)
95 95  ** Arrows will be available to go to the previous/next day
96 -
97 97  * **Display events by category**: users can select a category and only events from that category will be displayed in the calendar
98 98  * **Jump to a specific date**
99 99  
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 -
102 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)
103 103  
101 +
104 104  == Settings ==
105 105  
106 -=== General ===
107 107  
108 -* Calendar **name**
109 -* **Owner**
110 -* **Description**
111 -* **Location**
112 -
113 -* Select language?
114 -* Select from different time zones?
115 -* Select date format?
116 -* Select time format?
117 -
118 -* Week starts on Sunday/Monday/Saturday
119 -* Show events you have declined: Yes/No
120 -* Automatically add invitations to my calendar: Yes/No
121 -
122 -=== Privacy ===
123 -
124 -**Privacy settings for calendar**
125 -The calendar can be:
126 -
127 -* Public
128 -* Visible for specific wiki users -> Share calendar
129 -* Private
130 -
131 -**Default privacy settings for events**
132 -Events can be
133 -
134 -* Public: visible to everyone specified in the calendar settings
135 -* Private: visible only to the event creator
136 -
137 -=== Notifications ===
138 -
139 -A calendar owner may choose to receive notifications for:
140 -
141 -|=Events he is invited to |=Events he owns
142 -|(((
143 -* New invitations
144 -* Changed invitations
145 -* Canceled invitations
146 -* Invitation replies
147 -)))|(((
148 -* RSVPs from guests (attending, canceling presence)
149 -* Attachments being added
150 -* Comments being added
151 -)))
152 -
153 -In addition, **reminders** can be **sent by default to the calendar owner** via email **n** minutes/hours/days/weeks before the event (n = a number the calendar owner fills in; minutes/hours/days/weeks are options in a drop-down).
154 -
155 -== Search ==
156 -
157 -The "View event list" livetable can be used to filter events by date, location, and even to do searches within the event descriptions.
158 -
159 159  == Suggestions ==
160 160  
161 161  * Ability to print calendar
162 162  * Keyboard shortcuts
163 163  * Tips or link to documentation
164 -* Notifications by SMS could be interesting
165 165  * Gadget integration
166 166  
112 +
167 167  = Technicalities =
168 168  
169 169  The event-calendar part of the application will be implemented in the following way:
... ... @@ -178,12 +178,13 @@
178 178  * description (Description: text): // a short description of the event//
179 179  * location (Location: text): // the location where the event will take place//
180 180  * startDate (Start date: date(dd/MM/yyy)): // the date when the event starts//
181 -* startTime (Start time: static list): // the hour when the event starts//
127 +* startTime (Start time: time? (HH/mm)): // the hour when the event starts//
182 182  * endDate (End date: date(dd/MM/yyyy)): // the date when the event ends//
183 -* endTime (End time: static list): //the hour when the event ends//
184 -* category(Category: database list): // the category of the event//
185 -* privacySettings(Privacy: static list): // set the event to be public (visible to everyone) or private (visible only to the user)//
186 -* notifications(notifications: bool): // indicates if the notifications are activated or not//
129 +* endTime (End time: time? (HH/mm)): //the hour when the event ends//
130 +* calendar(Calendar: text): // the calendar to which the event belongs (its space)//
131 +* category(Category: text): // the category of the event//
132 +* privacySettings(Privacy: text): // set the event to be public (visible to everyone) or private (visible only to the user)//
133 +* emailNotifications(Email Notifications: bool): // indicates if the notifications are activated or not//
187 187  * userNotifiationList(Users to receive notifications: ?): // the list of users to be notified about the event//
188 188  
189 189  Calendar class properties: