more triage

[git.ikiwiki.info.git] / doc / patchqueue / calendar_--_archive_browsing_via_a_calendar_frontend.mdwn

diff --git a/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn b/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn
index 0abe2c901f111f70d5eda935af16a25b546725d9..f3a8b2f780067d9c9081a9d663c369b9a05d38bc 100644 (file)
--- a/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn
+++ b/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn
@@ -1,3 +1,13 @@
+I am serving notice that I am starting work on a calendar plugin inspired by Blosxom's calendar plugin. The current plan is to create a plugin that looks through all the source files matching a certain pagespec, and optionally spit out a month view for the specified month (default to current), or spit out a year view for a given year (defaulting to the current year), of a list  of year with posts in them. The output would be a table, with the same CSS directives that the Blosxom plugin used to use (so that I can just reuse my css file).  The links would be created to a $config{archivedir}/$year or $config{archivedir}/$year-$month file, which can just have 
+
+     \[[inline pages="blog/* and !*/Discussion and creation_year($year) and creation_month($month)" rss="no" atom="no" show="0"]]
+
+or some thing to generate a archive of postings. 
+
+Roland Mas suggested a separate cron job to generate these archive indices automatically, but that is another thread.
+
+ManojSrivastava
+
 This plugin is inspired by the calendar plugin for Blosxom, but derivesno code from it. This plugin is essentially a fancy front end to archives of previous pages, usually used for blogs. It can produce a calendar for a given month, or a list of months for a given year. To invoke the calendar, just use the preprocessor directive:
 
      \[[calendar ]]
@@ -119,8 +129,8 @@ annual and monthly indices, for example, by using something like this
 sample from my I<archives/2006/01.mdwn> (warning: line split for
 readability):
 
-   [[meta title="Archives for 2006/01"]]
-   [[inline rootpage="blog" atom="no" rss="no" show="0"
+   \[[meta title="Archives for 2006/01"]]
+   \[[inline rootpage="blog" atom="no" rss="no" show="0"
      pages="blog/* and !*/Discussion and creation_year(2006)
             and creation_month(01)"
    ]]
@@ -593,16 +603,16 @@ I've been looking over the calendar plugin. Some items:
   that emitting the whole calendar in the preprocess hook would simplify
   things and you'd not need to save state about calendars.
 
-> A) I am scared of the html scrubber, and have never turned it on,
+> I am scared of the html scrubber, and have never turned it on,
 >        and did not look too deeply into what would be scrubbed out --ManojSrivastava
 >> Unless you're using javascript, a few annoyances link <blink>, or inline
 >> css, it's unlikly to object to any html you might write. The list of
 >> allowed tags and attributes is easy to find near the top of the plugin.
 
->     B) In case the option that gets the ctime of the pages from the
->        SCM itself, %IkiWiki::pagectime  is not populated that early,
->        is it? So I waited until the last possible moment to look at
->        the time information.
+> In case the option that gets the ctime of the pages from the
+> SCM itself, %IkiWiki::pagectime  is not populated that early,
+> is it? So I waited until the last possible moment to look at
+> the time information.
 >
 >> Actually, since my big rewrite of the rendering path a few months ago,
 >> ikiwiki scans and populates almost all page information before starting