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