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