1.1 --- a/TO_DO.txt Wed Jul 20 00:53:40 2011 +0200
1.2 +++ b/TO_DO.txt Sat Jul 23 15:59:27 2011 +0200
1.3 @@ -1,11 +1,25 @@
1.4 +Points in Time
1.5 +--------------
1.6 +
1.7 +Events which have identical start and end times might be represented by
1.8 +building a calendar scale that distinguishes between times acting as start
1.9 +times and times acting as end times.
1.10 +
1.11 +Consider making dates convertible to timespans of the form (start of day,
1.12 +start of next day).
1.13 +
1.14 GriCal and External Aggregation
1.15 -------------------------------
1.16
1.17 +Make URL parameterisation robust enough to prevent arbitrary URL fragment
1.18 +insertion.
1.19 +
1.20 Support a linkToEvent method on Event instances, possibly just delegating to
1.21 linkToPage for Wiki events (although event sections could provide anchors for
1.22 -events in Wiki pages).
1.23 +events in Wiki pages). Calendar events would provide their own URL property.
1.24
1.25 -Support caching and proper encoding detection.
1.26 +Support caching and proper encoding detection. Response metadata could be
1.27 +inspected, defaulting to UTF-8 if necessary.
1.28
1.29 Support navigation where the full extent of external events cannot be
1.30 detected.
1.31 @@ -42,6 +56,12 @@
1.32 Map Views
1.33 ---------
1.34
1.35 +Explicit latitude and longitude values (such as the iCalendar GEO property)
1.36 +could be supported.
1.37 +
1.38 +Other projections might be supported. This would be necessary for various
1.39 +retrieved map images.
1.40 +
1.41 Dynamic images obtained from other sites or generated locally might provide some
1.42 enhancements to the map view. For example, a weather/radar image might show the
1.43 cloud or rain forecast either for the current situation or, if forecasts are