paul@290 | 1 | Navigation Controls
|
paul@290 | 2 | -------------------
|
paul@290 | 3 |
|
paul@291 | 4 | Without a calendar start, end and calendar name, the list view still shows
|
paul@291 | 5 | navigation controls. Also, links to other views from the day view can override
|
paul@291 | 6 | the default "all events" limits, which is not necessarily beneficial.
|
paul@290 | 7 |
|
paul@290 | 8 | The "New event" link should probably not be present when only remote events
|
paul@290 | 9 | are being aggregated by a calendar.
|
paul@290 | 10 |
|
paul@218 | 11 | Points in Time
|
paul@218 | 12 | --------------
|
paul@218 | 13 |
|
paul@218 | 14 | Events which have identical start and end times might be represented by
|
paul@218 | 15 | building a calendar scale that distinguishes between times acting as start
|
paul@290 | 16 | times and times acting as end times. (The iCalendar specification appears to
|
paul@290 | 17 | state that events without end dates/times are actually points in time, but
|
paul@290 | 18 | this potentially conflicts with the expectation that merely specifying a start
|
paul@290 | 19 | date or time produces an event with an undefined end point or a "common sense"
|
paul@290 | 20 | end point.)
|
paul@218 | 21 |
|
paul@218 | 22 | Consider making dates convertible to timespans of the form (start of day,
|
paul@218 | 23 | start of next day).
|
paul@218 | 24 |
|
paul@231 | 25 | Location Selection
|
paul@231 | 26 | ------------------
|
paul@217 | 27 |
|
paul@231 | 28 | A menu of locations derived from the EventLocationsDict could be shown by the
|
paul@231 | 29 | new event action.
|
paul@217 | 30 |
|
paul@211 | 31 | Localised Keywords
|
paul@211 | 32 | ------------------
|
paul@211 | 33 |
|
paul@211 | 34 | It should be possible to define events using localised equivalents of "start",
|
paul@211 | 35 | "end", "summary" and so on. To achieve this, the page language would be found
|
paul@211 | 36 | and regular expressions built to use the localised keywords, falling back on
|
paul@211 | 37 | the English keywords, would then search for event details.
|
paul@211 | 38 |
|
paul@211 | 39 | Recurring Events
|
paul@211 | 40 | ----------------
|
paul@211 | 41 |
|
paul@232 | 42 | Recurring event information from iCalendar sources should be considered in
|
paul@232 | 43 | order to avoid showing incomplete or incorrect event datetimes. Ultimately,
|
paul@232 | 44 | such information may need to be parsed and incorporated into the general event
|
paul@232 | 45 | recurrence processing.
|
paul@232 | 46 |
|
paul@211 | 47 | Having events recur at certain intervals would potentially involve the
|
paul@211 | 48 | expansion of events to produce multiple instances within a specified period of
|
paul@211 | 49 | interest, and such expansion could occur after an event's details have been
|
paul@211 | 50 | read. Care would need to be taken in cases where no limits are placed on a
|
paul@211 | 51 | calendar: the expanded instances should not be allowed to recede into the past
|
paul@211 | 52 | and future indefinitely; where no other events exist to provide implicit
|
paul@211 | 53 | limits, some other default limits might be required to let the expansion
|
paul@211 | 54 | occur.
|
paul@211 | 55 |
|
paul@211 | 56 | The description of recurring events could be based on the iCalendar
|
paul@211 | 57 | specification, although simpler schemes could be preferable. Recurring event
|
paul@211 | 58 | descriptions might start with "every" and then provide a time period ("day",
|
paul@211 | 59 | "week", "month", "year") for offsets from a specified date or time, perhaps
|
paul@211 | 60 | using qualifiers ("first", "second", "other", and so on), or instead provide a
|
paul@211 | 61 | more complete description using additional qualifiers that may override any
|
paul@211 | 62 | specified date or time for instances other than the primary occurrence. For
|
paul@211 | 63 | example, "every second Wednesday of every other month".
|
paul@211 | 64 |
|
paul@227 | 65 | Possible grammar:
|
paul@227 | 66 |
|
paul@227 | 67 | <recurrence> [ of <recurrence> ]...
|
paul@227 | 68 | [ from <datetime> ]
|
paul@227 | 69 | [ until <datetime> ]
|
paul@227 | 70 |
|
paul@227 | 71 | recurrence = every [ <qualifier> ] <interval>
|
paul@227 | 72 | interval = second | minute | hour | day | <weekday> | week | month | year
|
paul@227 | 73 |
|
paul@227 | 74 | The resolution of each successive <recurrence> must be lower than those it
|
paul@227 | 75 | follows. Thus, "every second day of every second week..." is valid whereas
|
paul@227 | 76 | "every second week of every second day..." is not.
|
paul@227 | 77 |
|
paul@204 | 78 | Map Views
|
paul@204 | 79 | ---------
|
paul@204 | 80 |
|
paul@218 | 81 | Other projections might be supported. This would be necessary for various
|
paul@218 | 82 | retrieved map images.
|
paul@218 | 83 |
|
paul@204 | 84 | Dynamic images obtained from other sites or generated locally might provide some
|
paul@204 | 85 | enhancements to the map view. For example, a weather/radar image might show the
|
paul@204 | 86 | cloud or rain forecast either for the current situation or, if forecasts are
|
paul@204 | 87 | available, for the times of events shown.
|
paul@204 | 88 |
|
paul@204 | 89 | Consider having day numbers down the side of a map view with highlighted days
|
paul@204 | 90 | indicating days having events, and with pop-up elements shown upon hovering over
|
paul@204 | 91 | each highlighted day.
|
paul@204 | 92 |
|
paul@204 | 93 | To Do Items
|
paul@204 | 94 | -----------
|
paul@204 | 95 |
|
paul@204 | 96 | Consider adding support for "to do" items. These might have time-related details
|
paul@204 | 97 | such as deadlines, but are more likely to have relationships with other items,
|
paul@204 | 98 | potentially forming a hierarchy of items.
|
paul@204 | 99 |
|
paul@204 | 100 | Event Section Parser
|
paul@204 | 101 | --------------------
|
paul@204 | 102 |
|
paul@204 | 103 | Events could be described using a Wiki section, potentially retaining the
|
paul@204 | 104 | definition list syntax for consistency with the current method of describing
|
paul@204 | 105 | events:
|
paul@204 | 106 |
|
paul@204 | 107 | {{{#!event
|
paul@204 | 108 | Start:: 2011-06-07
|
paul@204 | 109 | End:: 2011-06-07
|
paul@204 | 110 | Summary:: Event inside a section
|
paul@204 | 111 | }}}
|
paul@204 | 112 |
|
paul@204 | 113 | Such events could then be presented using more sophisticated methods and
|
paul@205 | 114 | potentially be editable. To support direct editing, the parser would provide
|
paul@205 | 115 | a hidden form field indicating the location of the section in the Wiki text,
|
paul@205 | 116 | and the new event action would be enhanced to read existing events from the
|
paul@205 | 117 | indicated page region, populating the form fields with the data found in the
|
paul@205 | 118 | page.
|
paul@220 | 119 |
|
paul@220 | 120 | Enhance the linkToEvent method on Event instances so that event sections can
|
paul@220 | 121 | provide anchors for events in Wiki pages.
|
paul@242 | 122 |
|
paul@242 | 123 | UID Properties
|
paul@242 | 124 | --------------
|
paul@242 | 125 |
|
paul@242 | 126 | Especially in the case of aggregation from multiple sources, the only reliable
|
paul@242 | 127 | way of avoiding repetition of the same events described in different places is
|
paul@242 | 128 | for authors to include a UID property identifying each event, using the same
|
paul@242 | 129 | value regardless of where the event is being published.
|
paul@265 | 130 |
|
paul@265 | 131 | Remote Source Timeouts
|
paul@265 | 132 | ----------------------
|
paul@265 | 133 |
|
paul@265 | 134 | Sometimes, network problems can cause delays in accessing remote sources. The
|
paul@265 | 135 | library should support either a timeout mechanism or asynchronous retrieval of
|
paul@265 | 136 | remote source data.
|