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