summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-06-26 16:26:08 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-06-26 16:26:08 -0400
commitd48d73ed866cb477c3ecb6ef9e519e899cfc5fe1 (patch)
tree1aca7adfdbfdeb9f9a8f6a64d51e01c696b56f1c
parent11e24ff0dd27d9d87ce0b46f68b8d84eae110e7f (diff)
response
-rw-r--r--doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn b/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn
index e4cc28e8a..7ce98aff7 100644
--- a/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn
+++ b/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn
@@ -29,6 +29,11 @@ That date will be used instead of the post creation time when displaying the cal
>> up on the calendar based on an arbitrary date. Perhaps this should be re-considered
>> as a separate plugin?
+>>> I think it makes sense to have only one calendar, if possible.
+>>> I think your event stuff is fine, the only thing we might want to add
+>>> is a config option for the calendar, to control whether it looks at the
+>>> event date, or the creation date. --[[Joey]]
+
--- calendar.pm.orig 2008-06-24 22:36:09.000000000 -0400
+++ calendar.pm 2008-06-24 22:51:11.000000000 -0400
@@ -23,6 +23,7 @@