1 Navigation Controls
2 -------------------
3
4 Without a calendar start and end and calendar name, the list view still shows
5 navigation controls.
6
7 The "New event" link should probably not be present when only remote events
8 are being aggregated by a calendar.
9
10 Points in Time
11 --------------
12
13 Events which have identical start and end times might be represented by
14 building a calendar scale that distinguishes between times acting as start
15 times and times acting as end times. (The iCalendar specification appears to
16 state that events without end dates/times are actually points in time, but
17 this potentially conflicts with the expectation that merely specifying a start
18 date or time produces an event with an undefined end point or a "common sense"
19 end point.)
20
21 Consider making dates convertible to timespans of the form (start of day,
22 start of next day).
23
24 Location Selection
25 ------------------
26
27 A menu of locations derived from the EventLocationsDict could be shown by the
28 new event action.
29
30 Localised Keywords
31 ------------------
32
33 It should be possible to define events using localised equivalents of "start",
34 "end", "summary" and so on. To achieve this, the page language would be found
35 and regular expressions built to use the localised keywords, falling back on
36 the English keywords, would then search for event details.
37
38 Recurring Events
39 ----------------
40
41 Recurring event information from iCalendar sources should be considered in
42 order to avoid showing incomplete or incorrect event datetimes. Ultimately,
43 such information may need to be parsed and incorporated into the general event
44 recurrence processing.
45
46 Having events recur at certain intervals would potentially involve the
47 expansion of events to produce multiple instances within a specified period of
48 interest, and such expansion could occur after an event's details have been
49 read. Care would need to be taken in cases where no limits are placed on a
50 calendar: the expanded instances should not be allowed to recede into the past
51 and future indefinitely; where no other events exist to provide implicit
52 limits, some other default limits might be required to let the expansion
53 occur.
54
55 The description of recurring events could be based on the iCalendar
56 specification, although simpler schemes could be preferable. Recurring event
57 descriptions might start with "every" and then provide a time period ("day",
58 "week", "month", "year") for offsets from a specified date or time, perhaps
59 using qualifiers ("first", "second", "other", and so on), or instead provide a
60 more complete description using additional qualifiers that may override any
61 specified date or time for instances other than the primary occurrence. For
62 example, "every second Wednesday of every other month".
63
64 Possible grammar:
65
66 <recurrence> [ of <recurrence> ]...
67 [ from <datetime> ]
68 [ until <datetime> ]
69
70 recurrence = every [ <qualifier> ] <interval>
71 interval = second | minute | hour | day | <weekday> | week | month | year
72
73 The resolution of each successive <recurrence> must be lower than those it
74 follows. Thus, "every second day of every second week..." is valid whereas
75 "every second week of every second day..." is not.
76
77 Map Views
78 ---------
79
80 Other projections might be supported. This would be necessary for various
81 retrieved map images.
82
83 Dynamic images obtained from other sites or generated locally might provide some
84 enhancements to the map view. For example, a weather/radar image might show the
85 cloud or rain forecast either for the current situation or, if forecasts are
86 available, for the times of events shown.
87
88 Consider having day numbers down the side of a map view with highlighted days
89 indicating days having events, and with pop-up elements shown upon hovering over
90 each highlighted day.
91
92 To Do Items
93 -----------
94
95 Consider adding support for "to do" items. These might have time-related details
96 such as deadlines, but are more likely to have relationships with other items,
97 potentially forming a hierarchy of items.
98
99 Event Section Parser
100 --------------------
101
102 Events could be described using a Wiki section, potentially retaining the
103 definition list syntax for consistency with the current method of describing
104 events:
105
106 {{{#!event
107 Start:: 2011-06-07
108 End:: 2011-06-07
109 Summary:: Event inside a section
110 }}}
111
112 Such events could then be presented using more sophisticated methods and
113 potentially be editable. To support direct editing, the parser would provide
114 a hidden form field indicating the location of the section in the Wiki text,
115 and the new event action would be enhanced to read existing events from the
116 indicated page region, populating the form fields with the data found in the
117 page.
118
119 Enhance the linkToEvent method on Event instances so that event sections can
120 provide anchors for events in Wiki pages.
121
122 UID Properties
123 --------------
124
125 Especially in the case of aggregation from multiple sources, the only reliable
126 way of avoiding repetition of the same events described in different places is
127 for authors to include a UID property identifying each event, using the same
128 value regardless of where the event is being published.
129
130 Remote Source Timeouts
131 ----------------------
132
133 Sometimes, network problems can cause delays in accessing remote sources. The
134 library should support either a timeout mechanism or asynchronous retrieval of
135 remote source data.