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