1.1 --- a/EventAggregatorSupport.py Sat Feb 18 01:19:52 2012 +0100
1.2 +++ b/EventAggregatorSupport.py Sat Feb 18 16:37:58 2012 +0100
1.3 @@ -1443,7 +1443,7 @@
1.4 self.last = last
1.5 self.duration = last - first
1.6
1.7 - if self.calendar_name is not None:
1.8 + if self.calendar_name:
1.9
1.10 # Store the view parameters.
1.11
1.12 @@ -1932,7 +1932,7 @@
1.13
1.14 # Prepare navigation links.
1.15
1.16 - if self.calendar_name is not None:
1.17 + if self.calendar_name:
1.18 calendar_name = self.calendar_name
1.19
1.20 # Links to the previous set of months and to a calendar shifted
2.1 --- a/TO_DO.txt Sat Feb 18 01:19:52 2012 +0100
2.2 +++ b/TO_DO.txt Sat Feb 18 16:37:58 2012 +0100
2.3 @@ -1,9 +1,8 @@
2.4 Navigation Controls
2.5 -------------------
2.6
2.7 -Without a calendar start, end and calendar name, the list view still shows
2.8 -navigation controls. Also, links to other views from the day view can override
2.9 -the default "all events" limits, which is not necessarily beneficial.
2.10 +Links to other views from the day view can override the default "all events"
2.11 +limits, which is not necessarily beneficial.
2.12
2.13 The "New event" link should probably not be present when only remote events
2.14 are being aggregated by a calendar.
2.15 @@ -128,6 +127,15 @@
2.16 for authors to include a UID property identifying each event, using the same
2.17 value regardless of where the event is being published.
2.18
2.19 +Formatting in iCalendar Output
2.20 +------------------------------
2.21 +
2.22 +If there is a reasonably standard way of incorporating Wiki text in iCalendar
2.23 +output alongside plain text, this would enable events aggregated from Wiki
2.24 +sources to use Wiki text to describe things like the location and topics of an
2.25 +event with links and other formatting that could then be reproduced in the
2.26 +aggregating Wiki.
2.27 +
2.28 Remote Source Timeouts
2.29 ----------------------
2.30