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 GriCal and External Aggregation
12 -------------------------------
13
14 Support caching of remote event data.
15
16 Support navigation where the full extent of external events cannot be
17 detected.
18
19 Localised Keywords
20 ------------------
21
22 It should be possible to define events using localised equivalents of "start",
23 "end", "summary" and so on. To achieve this, the page language would be found
24 and regular expressions built to use the localised keywords, falling back on
25 the English keywords, would then search for event details.
26
27 Recurring Events
28 ----------------
29
30 Having events recur at certain intervals would potentially involve the
31 expansion of events to produce multiple instances within a specified period of
32 interest, and such expansion could occur after an event's details have been
33 read. Care would need to be taken in cases where no limits are placed on a
34 calendar: the expanded instances should not be allowed to recede into the past
35 and future indefinitely; where no other events exist to provide implicit
36 limits, some other default limits might be required to let the expansion
37 occur.
38
39 The description of recurring events could be based on the iCalendar
40 specification, although simpler schemes could be preferable. Recurring event
41 descriptions might start with "every" and then provide a time period ("day",
42 "week", "month", "year") for offsets from a specified date or time, perhaps
43 using qualifiers ("first", "second", "other", and so on), or instead provide a
44 more complete description using additional qualifiers that may override any
45 specified date or time for instances other than the primary occurrence. For
46 example, "every second Wednesday of every other month".
47
48 Map Views
49 ---------
50
51 Explicit latitude and longitude values (such as the iCalendar GEO property)
52 could be supported.
53
54 Other projections might be supported. This would be necessary for various
55 retrieved map images.
56
57 Dynamic images obtained from other sites or generated locally might provide some
58 enhancements to the map view. For example, a weather/radar image might show the
59 cloud or rain forecast either for the current situation or, if forecasts are
60 available, for the times of events shown.
61
62 Consider having day numbers down the side of a map view with highlighted days
63 indicating days having events, and with pop-up elements shown upon hovering over
64 each highlighted day.
65
66 To Do Items
67 -----------
68
69 Consider adding support for "to do" items. These might have time-related details
70 such as deadlines, but are more likely to have relationships with other items,
71 potentially forming a hierarchy of items.
72
73 Event Section Parser
74 --------------------
75
76 Events could be described using a Wiki section, potentially retaining the
77 definition list syntax for consistency with the current method of describing
78 events:
79
80 {{{#!event
81 Start:: 2011-06-07
82 End:: 2011-06-07
83 Summary:: Event inside a section
84 }}}
85
86 Such events could then be presented using more sophisticated methods and
87 potentially be editable. To support direct editing, the parser would provide
88 a hidden form field indicating the location of the section in the Wiki text,
89 and the new event action would be enhanced to read existing events from the
90 indicated page region, populating the form fields with the data found in the
91 page.
92
93 Enhance the linkToEvent method on Event instances so that event sections can
94 provide anchors for events in Wiki pages.