Skip to Content

Changes for page Calendar Application

Last modified by Ecaterina Valica on 2014/01/15 13:50
From version 9.5
edited by Silvia Rusu
on 2011/06/20 13:24
Change comment: There is no comment for this version
To version 7.1
edited by Vlad Merticariu
on 2011/06/17 10:14
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,85 +32,6 @@
32 32  * Each event must be stored in its own document
33 33  * Have different calendars for each space
34 34  
35 -= Detailed Functionality =
36 -
37 -== Adding events ==
38 -
39 -You may add an event by:
40 -
41 -1. Clicking a button which opens a modal window, allowing the user to insert details and save
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 -
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 -
46 -* **Name**
47 -* **Date**: User should be able to mark an event as **recurring**. Similarly to Google Calendar, event recurrence should be customizable
48 -* **Location**: Link to Google Maps
49 -* **Description**
50 -* **Category**
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.
53 -* **Privacy options**: Default, Private, Public
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 -* **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
56 -* **Attachments**: Documents can be attached to an event. An icon will indicate in the daily and weekly view modes that the event has attachments
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 -
59 -**More actions:**
60 -
61 -* **Change owner**
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 -* **Delete event**
64 -* **Duplicate event**: Copy an event inside the calendar
65 -* **Copy event to a different calendar**: Copy an event from the current calendar to a different calendar
66 -
67 -== Viewing events ==
68 -
69 -**View calendar:**
70 -
71 -* Tabbed day, week, month, yearly view
72 -* **Year view**:
73 -** There should be 12 cells representing the 12 different months
74 -** When users click on a month (e.g. //June 2011//) they should be directed to that specific month in the "Month" tab
75 -** When users click on a day (e.g. //1//) they should be directed to that specific day in the "Day" tab
76 -** Days that have events associated should be marked with bold
77 -** The current day should be highlighted with a distinct color or frame
78 -** Arrows will be available to go to the previous/next year
79 -* **Month view**:
80 -** Table view; each column represents a day of the week (Monday, Tuesday...); each cell represents a specific date (1, 2...)
81 -** When users click on a day (e.g. //1// in the cell header) they should be directed to that specific day in the "Day" tab
82 -** Events should be displayed chronologically inside each cell. The starting hour of the event should be displayed, the name of the event and an icon indicating if notifications have been set. Clicking or hovering (TBD) on the event will bring up a pop-up with more details and links to edit and delete the event
83 -** The current day should be highlighted with a distinct color (same as the one used for the "Year" view)
84 -** Arrows will be available to go to the previous/next month
85 -* **Week view**
86 -** Table view; each column represents a day of the week (Monday, Tuesday...); each row represents an hour of the day
87 -** When users click on a day (e.g. //Fri 6/17// in the table header) they should be directed to that specific day in the "Day" tab
88 -** Events should be displayed chronologically in each column 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
89 -** The current day should be highlighted with a distinct color (same as the one used for the other views)
90 -** Arrows will be available to go to the previous/next week
91 -* **Day view**
92 -** Table view; one column representing one day; each row represents an hour of the day
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 -** The current day should be highlighted with a distinct color (same as the one used for the other views)
95 -** Arrows will be available to go to the previous/next day
96 -
97 -* **Display events by category**: users can select a category and only events from that category will be displayed in the calendar
98 -* **Jump to a specific date**
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 -**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 -
104 -== Settings ==
105 -
106 -
107 -== Suggestions ==
108 -
109 -* Ability to print calendar
110 -* Keyboard shortcuts
111 -* Tips or link to documentation
112 -* Gadget integration
113 -
114 114  = Technicalities =
115 115  
116 116  The event-calendar part of the application will be implemented in the following way:
... ... @@ -125,12 +125,13 @@
125 125  * description (Description: text): // a short description of the event//
126 126  * location (Location: text): // the location where the event will take place//
127 127  * startDate (Start date: date(dd/MM/yyy)): // the date when the event starts//
128 -* startTime (Start time: static list): // the hour when the event starts//
49 +* startTime (Start time: time? (HH/mm)): // the hour when the event starts//
129 129  * endDate (End date: date(dd/MM/yyyy)): // the date when the event ends//
130 -* endTime (End time: static list): //the hour when the event ends//
131 -* category(Category: database list): // the category of the event//
132 -* privacySettings(Privacy: static list): // set the event to be public (visible to everyone) or private (visible only to the user)//
133 -* notifications(notifications: bool): // indicates if the notifications are activated or not//
51 +* endTime (End time: time? (HH/mm)): //the hour when the event ends//
52 +* calendar(Calendar: text): // the calendar to which the event belongs (its space)//
53 +* category(Category: text): // the category of the event//
54 +* privacySettings(Privacy Settings: text): // set the event to be public (visible to everyone) or private (visible only to the user)//
55 +* emailNotifications(Email Notifications: bool): // indicates if the notifications are activated or not//
134 134  * userNotifiationList(Users to receive notifications: ?): // the list of users to be notified about the event//
135 135  
136 136  Calendar class properties:
... ... @@ -137,7 +137,6 @@
137 137  
138 138  * title (Title: text): // the title of the calendar//
139 139  * description(Description: text): // a short description of the calendar//
140 -* privacySettings(Privacy: static list): // set the calendar to be public(visible to everyone) or private(visisble only to the user)//
141 141  * owner(Owner: user): // the user who owns the calendar//
142 142  
143 143  Calendar class sheets: