responses du jour

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index d5444768cbf16cf87e9c69d1636b428f5b571971..4f8ead729651feac762a035bf0f9fd1a2705a75c 100644 (file)
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -48,6 +48,9 @@ the files and then it *did* compile but 'touch'ing the files after a few minutes
 > OK, thanks, I don't quite know what was happening before but it seems to be working right now.
 > --[[Chris]]
 
 > OK, thanks, I don't quite know what was happening before but it seems to be working right now.
 > --[[Chris]]
 

+>> Weird. I wish I knew what happened, but as it's working now, I'm
+>> guessing some kind of user error was involved. --[[Joey]]
+

 * I wish there was a mailing list, much easier for this sort of stuff than this, apart from
 anything else I get to use a decent editor.
 
 * I wish there was a mailing list, much easier for this sort of stuff than this, apart from
 anything else I get to use a decent editor.
 


@@ -99,7 +102,7 @@ something, that I think is very valuable.
 >>> Or you could just use apache or whatever and set up the access controls
 >>> there. Of course, that wouldn't integrate very well with the wiki,
 >>> unless perhaps you decided to use http basic authentication and the
 >>> Or you could just use apache or whatever and set up the access controls
 >>> there. Of course, that wouldn't integrate very well with the wiki,
 >>> unless perhaps you decided to use http basic authentication and the

->>> httpauth plugin for ikiwiki that integrates with that.. [[--Joey]]
+>>> httpauth plugin for ikiwiki that integrates with that.. --[[Joey]]

 
 >>>> Which would rule out openid, or other fun forms of auth. And routing all access 
 >>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]]
 
 >>>> Which would rule out openid, or other fun forms of auth. And routing all access 
 >>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]]


@@ -143,6 +146,10 @@ with all news or the one with the latest news only, I don't know yet.)
 
 Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?
 
 
 Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?
 

+> No, but it should be quite easy to write such a plugin. The otl plugin
+> is a good example of writing a formatting plugin that uses an external
+> conversion program, like asciidoc or txt2tags. --[[Joey]]
+

 ----
 
 # LaTeX support?
 ----
 
 # LaTeX support?


@@ -150,21 +157,38 @@ Any plugins or support for using asciidoc or txt2tags as the wiki language and/o
 Any plugins or support for exporting to LaTeX?
 (If not could use asciidoc or txt2tags mentioned above to generated LaTeX.)
 
 Any plugins or support for exporting to LaTeX?
 (If not could use asciidoc or txt2tags mentioned above to generated LaTeX.)
 

+> It's already [[been_requested|todo/latex]], although perhaps not
+> working the way you're thinking of. Noone is currently working on it.
+> --[[Joey]]
+

 ----
 
 # Using with RCS?
 
 Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki?
 
 ----
 
 # Using with RCS?
 
 Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki?
 

+> I don't belive that RCS offers enough SCM features to be useable as a
+> fullfledged backend to ikiwiki. For one thing, there's no way to have
+> hook scripts run when changes are ci'd, is there? So you'd have to ci and
+> then manually run ikiwiki. It should be possible to do an RCS backend
+> that supports web commits with ci, and history (parsing the rcs files by
+> hand?). If you're a masochist. :-) --[[Joey]]
+

 ----
 
 # Using with CVS?
 
 Any examples of using ikiwiki with cvs?
 
 ----
 
 # Using with CVS?
 
 Any examples of using ikiwiki with cvs?
 

+> No, although the existing svn backend could fairly esily be modified into
+> a CVS backend, by someone who doesn't mind working with CVS. --[[Joey]]
+

 ----
 
 # Show differences before saving page?
 
 It would be nice to be able to have a button to show "Differences" (or "Show Diff") when
 ----
 
 # Show differences before saving page?
 
 It would be nice to be able to have a button to show "Differences" (or "Show Diff") when

-editing a page. Is that an option that can be enabled?
\ No newline at end of file
+editing a page. Is that an option that can be enabled?
+
+> It's doable, it could even be done by a [[todo/plugin]], I think.
+> --[[Joey]]

diff --git a/doc/todo/plugin.mdwn b/doc/todo/plugin.mdwn
index fdd37d95491c91f3e89b9e875ba90aa41c6eb9ff..4e6385d3893e17c5286f4cc7ea57d541b1de6bbe 100644 (file)
--- a/doc/todo/plugin.mdwn
+++ b/doc/todo/plugin.mdwn
@@ -13,6 +13,8 @@ Suggestions of ideas for plugins:
   to inline the cgi, although firefox seems to render that nastily with
   nested scroll bars. :-(
 
   to inline the cgi, although firefox seems to render that nastily with
   nested scroll bars. :-(
 

+* 
+

 * For PlaceWiki I want to be able to do some custom plugins, including one
   that links together subpages about the same place created by different
   users. This seems to call for a plugin that applies to every page w/o any
 * For PlaceWiki I want to be able to do some custom plugins, including one
   that links together subpages about the same place created by different
   users. This seems to call for a plugin that applies to every page w/o any


@@ -28,7 +30,5 @@ Suggestions of ideas for plugins:
 
 All the kinds of plugins that blogging software has is also a possibility:
 
 
 All the kinds of plugins that blogging software has is also a possibility:
 

-* Blog post calendar
-

 * How about an event calendar. Events could be sub-pages with an embedded 
 * How about an event calendar. Events could be sub-pages with an embedded 

- code to detail recurrance and/or event date/time
+  code to detail recurrance and/or event date/time