gtd plugin by Michael Klier
This plugin implements a nice formatted easy to use todo list following the principles of GTD
Last updated on 2008-02-13. Provides Syntax.
Compatible with DokuWiki devel > 2007-06-26 > 2006-11-06.
Similar to task.
| Download | plugin-gtd.tgz |
|---|
This plugin implements a nice formatted easy to use todo list following the principles of GTD.
Download the archive and unpack it into <dokuwiki>/lib/plugins.
The plugin is also available via darcs.
% cd <dokuwiki>/lib/plugins % darcs get http://chimeric.de/_dev/darcs/dokuwiki/plugins/gtd
You can set a default context which will be used if no context was given via the DokuWiki configuration manager.
<gtd [warn=dd] [due=dd]> [#] [@context] [p:project] [d:yyyy-mm-dd|mm-dd|dd] [w:dd] [describing text] [#] [@context] [p:project] [d:yyyy-mm-dd|mm-dd|dd] [w:dd] [describing text] </gtd>
| [warn=dd] | set a global warning period in days before the task has to be finished, the item changes its' color to orange | optional (defaults to 5) |
|---|---|---|
| [due=dd] | set a global due to period in days before the task has to be finished, the item changes its' color to red | optional (defaults to 2) |
| [#] | A leading '#' marks a Todo as done | optional |
| [@context] | The context of the Todo ( _ will be transformed to space ). | required |
| [p:project] | Specifies if a todo item belongs to a certain project ( _ will be transformed to space ). | optional |
| [w:dd] | overwrite global warning period by days | optional |
| [d:yyyy-mm-dd] | The date until when the task should be done, if you use mm-dd the year will be appended automatically, same if you only use dd the month and the year will be appended automatically | optional |
| [describing text] | Describing text. Must be on a new (one linebreak) line (Wiki Syntax can be used to format). | required |
You can try the plugin here.
Please report bugs at the Bug Tracker.
A way to have spaces in the list name (@context) would be nice. Also having multi-line descriptions would be helpful as well. I'm not sure how to go about doing that without having too complicated syntax that would get in the way of usability. No biggie. - GJH
Done, “_” will be translated to space. Multi-line descriptions are also possible using ”\\”. — Michael Klier 16.01.2007 23:07
Oh, perfect, I was using underscores to space it out anyway. Thanks. The double backslash does work for multi-line, I thought I tried that but maybe not. One note on formatting - I added “padding: 0px 3px 0px 3px;” to span.plugin_gtd_over, span.plugin_gtd_upcoming and span.plugin_gtd_current which gives a little breathing room around the colored boxes so the text doesn't press right up against it. Check it out, see if you like it. Thanks again. - GJH 2007-01-18
I'd like to see a checkbox next to each incomplete to-do with an onchange JavaScript event that would both cross out the line and submit the edit automatically via AJAX. The ability to mark an item as done with a single click rather than clicking “edit”, typing [#], and clicking “save” would make this much more useful. — Scott Reynen 2007-03-07
Yes this would be nice, I think about it! — chi 21.03.2007 12:02
Sort data by context/project/date : it would be nice to sort the displayed data so I could append new lines at the end of the gtd block and not have to put them at the right place
It's ok for context/project but not for the date : nice when you have many items…— Marc 2007.11.26
That`s allready the case. You don`t need to put them at a specific page, when you assign the same context/project it will appear at the right place automatically. — chi 04.05.2007 14:29
It would be nice to have configuration options for output formatting - it it wasn´t headlines for context and project, one could use page links there (of course one could tweak the plugin´s code, but …). hh 18.10.2007 :45
It would be useful to have parameters to be able to fix the expiries, for example: <gtd warning=“5” due=“2”> — Marc 2007.11.26
Another nice feature : print the day of week near the due date : 2007-11-30 friday (or 2007-11-30 vendredi
) — Marc 2007.11.26
It would be also useful to be able to add the date of realization of the point, for example after the dash
#2007-11-26 @Quod p:Admin_[Ruth] thing to do 2007-11-29
— Marc 2007.11.26
Hi Marc, I like your ideas and will go on implementing them - I am not sure about the “fix expiries” can you explain it further please? — Michael Klier 30.11.2007 12:45
Hello Michael, “fix expiries” allows to modify the default behaviour of the plugin. Certain actions require more time to be carried out, therefore one must be informed more quickly. For example 20 days before the action must become orange (warning=“20”) and then 8 days before it must become red (due=“8”), other actions are quickly carried out, one can be informed very little time before the expiry (for example warning=“3” due=“1”). — Marc 2007.12.07
Hi Michael, after having used GTD during a few days, I encountered a - small - problem when the text comprises dates, for example: ”…need to make an invoice with the date 2007-12-31… 2007-12-15”. Its confusing… Maybe one can imagine syntax like this:
@Quod p:Admin_[Ruth] ...action with date 2007-12-31 and do something else.. d:2007-11-29 w:10 t:3
where d: is the due date, w: warning, t: time to do something… — Marc 2007.12.07
Heloo Michael, Happy new year ! Another request about “special dates” : it would be interesting that these dates can also be [dd] to be able to be used on a monthly basis (the month and year will be added automatically). Maybe the syntax need to be s: (for special…) — Marc 2008.01.11
Hi Marc, ok most of your ideas are implemented now, check it out and tell me what you think. — Michael Klier 17.01.2008 23:33
Michael,
Whilst I appreciate the utility of the recent additions to this syntax plugin, I would have also greatly appreciated it if they were not implemented in such a way that they broke existing pages on my company Wiki when I updated my local install of the plugin. As it is, I'm going to have to backlevel my local system now to make it work. I do not have time, nor think that it should be necessary, to update all of the pages on the wiki using this plugin by hand each time it is updated. — DDN 2008.02.07
DDN,
I am deeply sorry. I know this wasn't the most comfortable way for everybody using this plugin. However, since the plugin does rely on wiki syntax itself, it's rather complicated to introduce new features without breaking something. It would be rather complicated to implement a procedure to the let plugin auto-detect pages with deprecated syntax and let it re-parse them. Again, I am sorry for the trouble you have, and I think it won't happen again anytime soon. — Michael Klier 12.02.2008 16:04
Hello Michael, works fine for me ! Thanks, Marc — Marc 2008.02.20
Hi, the plugin does not display tasks with correct style information (somehow it does not find the style.css) in the latest dokuwiki release.
Probably a CSS cache issue, try forcing a recache withCTRL+SHIFT+Rin Firefox, or touch<dokuwiki>/conf/dokuwiki.php.Hm no, this did not work either - the tasks are looking just like an ordinary unordered list to me. I have made you a screenshot: http://imageupload.com/~imageupl/show.php/148218_gtd.png.htmlMh it was indeed a cache issue - yeah I did the ctrl+shift+r before but it did not work… so I removed the cache header in /lib/exe/css.php and voila there it was XD
Hi
It would be nice to add these features per task:
Thanks
Dan
If you want to use more than 1 line for the description change:
list($params, $desc) = explode("\n", trim($line));
to
list($params, $desc) = explode("\n", trim($line),2);
in syntax.php
Golem
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported