what approach to take for pagination?

[git.ikiwiki.info.git] / doc / forum / managing_todo_lists.mdwn

diff --git a/doc/forum/managing_todo_lists.mdwn b/doc/forum/managing_todo_lists.mdwn
index b55420aca50eed5710524aba1b81e7967df4cb08..0a69af80524ef1326d18086850a4c72b21f7778f 100644 (file)
--- a/doc/forum/managing_todo_lists.mdwn
+++ b/doc/forum/managing_todo_lists.mdwn
@@ -31,3 +31,14 @@ I envisage a button called "commit changes" appearing once some changes are
 made that submits the changes to the CGI, perhaps via a back channel. I'm not
 sure how to handle embeds or challenges from the CGI such as a login challenge
 (maybe the back channel would not be necessary in the first cut).
 made that submits the changes to the CGI, perhaps via a back channel. I'm not
 sure how to handle embeds or challenges from the CGI such as a login challenge
 (maybe the back channel would not be necessary in the first cut).

+
+> You might look at the [[plugins/hnb]] plugin. HNB supports checklists.
+> There's not a fancy web interface, but the hnb command-line program can
+> be used to edit them. --[[Joey]] 
+
+>> thanks - I'll give it a look. I spent a few hours writing some javascript to manipulate a ul/li DOM tree in an outliner-fashion the other day. I might be able to join the puzzle pieces together sometime. [[Jon]]
+
+a solution for this could be similar to a solution for [[todo/structured page data]], as todo lists are definitely a form of structured data. (in both cases, the page's current content is rendered into a html form, whose result is then saved as the page's new contents) --[[chrysn]]
+
+> Thanks for the link: yup, there's definitely some common ground there.
+> -- [[Jon]]