response

[git.ikiwiki.info.git] / doc / todo / plugin.mdwn

diff --git a/doc/todo/plugin.mdwn b/doc/todo/plugin.mdwn
index 323da5cbd30aa610ff29a01f4de89fa8da892b00..80cb29b71e0401631a3a7809fa655750297c8dac 100644 (file)
--- a/doc/todo/plugin.mdwn
+++ b/doc/todo/plugin.mdwn
@@ -1,9 +1,12 @@
 Suggestions of ideas for plugins:
 
 * list of registered users - tricky because it sorta calls for a way to rebuild the page when a new user is registered. Might be better as a cgi?
 Suggestions of ideas for plugins:
 
 * list of registered users - tricky because it sorta calls for a way to rebuild the page when a new user is registered. Might be better as a cgi?

-* a [[link_map]]
+> At best, this could only show the users who have logged in, not all
+> permitted by the current auth plugin(s).  HTTP auth would need
+> web-server-specific code to list all users, and openid can't feasibly do so
+> at all. --[[JoshTriplett]]
+

 * [[sigs]] ?
 * [[sigs]] ?

-* [[pageindexes]]

 
 * Support [[RecentChanges]] as a regular page containing a plugin that
   updates each time there is a change, and statically builds the recent
 
 * Support [[RecentChanges]] as a regular page containing a plugin that
   updates each time there is a change, and statically builds the recent


@@ -14,6 +17,14 @@ Suggestions of ideas for plugins:
   Or using an iframe
   to inline the cgi, although firefox seems to render that nastily with
   nested scroll bars. :-(
   Or using an iframe
   to inline the cgi, although firefox seems to render that nastily with
   nested scroll bars. :-(

+> Or just link to the equivalent in the version control system, if available;
+> gitweb's shortlog or summary view would work nicely as a
+> RecentChanges. --[[JoshTriplett]]
+>>Why not fork the process?  We wouldn't have to wait around for a response since we would assume the recent changes page was being generated correctly.
+
+* 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?
+  Using a plugin?

 
 * 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
 
 * 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


@@ -24,17 +35,25 @@ Suggestions of ideas for plugins:
   or something. It's possible that this is a special case of backlinks and
   is best implemented by making backlinks a plugin somehow. --[[Joey]]
 
   or something. It's possible that this is a special case of backlinks and
   is best implemented by making backlinks a plugin somehow. --[[Joey]]
 

-* interwiki links
-

 * random page (cgi plugin; how to link to it easily?)
 
 * random page (cgi plugin; how to link to it easily?)
 

-* navigation or side bar plugin, would use a specific page as the side bar
-  and include it into the other pages as specified by the template. The
-  pagetemplate hook was added to allow for this.
+* How about an event calendar. Events could be sub-pages with an embedded 
+  code to detail recurrance and/or event date/time
+
+* rcs plugin ([[JeremyReed]] has one he has been using for over a month with over 850 web commits with 13 users with over ten commits each.)

 
 

-All the kinds of plugins that blogging software has is also a possibility:
+* asciidoc or txt2tags format plugins

 
 

-* Blog post calendar
+  Should be quite easy to write, the otl plugin is a good example of a
+  similar formatter.

 
 

-* How about an event calendar. Events could be sub-pages with an embedded 
- code to detail recurrance and/or event date/time
+>>Isn't there a conflict between ikiwiki using \[\[  \]\] and asciidoc using the same?
+>>There is a start of an asciidoc plugin at <http://www.mail-archive.com/asciidoc-discuss@metaperl.com/msg00120.html>
+>>-- KarlMW
+
+* manpage plugin: convert **"ls(1)"** style content into Markdown like **\[ls(1)\]\(http://example.org/man.cgi?name=ls&sect=1\)** or into HTML directly.
+
+> With a full installation of groff available, man offers HTML output.  Might
+> take some fiddling to make it fit into the ikiwiki templates, and you might
+> or might not want to convert pages in the SEE ALSO as
+> well. --[[JoshTriplett]]