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