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