1 Navigation Controls
2 -------------------
3
4 The "New event" link should probably not be present when only remote events
5 are being aggregated by a calendar.
6
7 Improve the accessibility of controls by providing links with titles and
8 offering links as alternatives to pop-up elements.
9
10 Points in Time
11 --------------
12
13 Consider making dates convertible to timespans of the form (start of day,
14 start of next day).
15
16 Localised Keywords
17 ------------------
18
19 It should be possible to define events using localised equivalents of "start",
20 "end", "summary" and so on. To achieve this, the page language would be found
21 and regular expressions built to use the localised keywords, falling back on
22 the English keywords, would then search for event details.
23
24 Recurring Events
25 ----------------
26
27 Recurring event information from iCalendar sources should be considered in
28 order to avoid showing incomplete or incorrect event datetimes. Ultimately,
29 such information may need to be parsed and incorporated into the general event
30 recurrence processing.
31
32 Having events recur at certain intervals would potentially involve the
33 expansion of events to produce multiple instances within a specified period of
34 interest, and such expansion could occur after an event's details have been
35 read. Care would need to be taken in cases where no limits are placed on a
36 calendar: the expanded instances should not be allowed to recede into the past
37 and future indefinitely; where no other events exist to provide implicit
38 limits, some other default limits might be required to let the expansion
39 occur.
40
41 The description of recurring events could be based on the iCalendar
42 specification, although simpler schemes could be preferable. Recurring event
43 descriptions might start with "every" and then provide a time period ("day",
44 "week", "month", "year") for offsets from a specified date or time, perhaps
45 using qualifiers ("first", "second", "other", and so on), or instead provide a
46 more complete description using additional qualifiers that may override any
47 specified date or time for instances other than the primary occurrence. For
48 example, "every second Wednesday of every other month".
49
50 The resolution of each successive <recurrence> would need to be lower than
51 those it follows. Thus, "every second day of every second week..." would be
52 valid whereas "every second week of every second day..." would not.
53
54 Map Views
55 ---------
56
57 Other projections might be supported. This would be necessary for various
58 retrieved map images.
59
60 Dynamic images obtained from other sites or generated locally might provide some
61 enhancements to the map view. For example, a weather/radar image might show the
62 cloud or rain forecast either for the current situation or, if forecasts are
63 available, for the times of events shown.
64
65 Consider having day numbers down the side of a map view with highlighted days
66 indicating days having events, and with pop-up elements shown upon hovering over
67 each highlighted day.
68
69 To Do Items
70 -----------
71
72 Consider adding support for "to do" items. These might have time-related details
73 such as deadlines, but are more likely to have relationships with other items,
74 potentially forming a hierarchy of items.
75
76 Event Section Parser
77 --------------------
78
79 Events in page sections/regions could be presented using more sophisticated
80 methods and potentially be editable. To support direct editing, the parser
81 would provide a hidden form field indicating the location of the section in
82 the Wiki text, and the new event action would be enhanced to read existing
83 events from the indicated page region, populating the form fields with the
84 data found in the page.
85
86 UID Properties
87 --------------
88
89 Especially in the case of aggregation from multiple sources, the only reliable
90 way of avoiding repetition of the same events described in different places is
91 for authors to include a UID property identifying each event, using the same
92 value regardless of where the event is being published.
93
94 Formatting in iCalendar Output
95 ------------------------------
96
97 If there is a reasonably standard way of incorporating Wiki text in iCalendar
98 output alongside plain text, this would enable events aggregated from Wiki
99 sources to use Wiki text to describe things like the location and topics of an
100 event with links and other formatting that could then be reproduced in the
101 aggregating Wiki.
102
103 Remote Source Timeouts
104 ----------------------
105
106 Sometimes, network problems can cause delays in accessing remote sources. The
107 library should support either a timeout mechanism or asynchronous retrieval of
108 remote source data.