Summary: Talk page for the GTD Task List Manager recipe
Maintainer: Petko

Please add your comments about the GTD Task List Manager recipe here. --Petko June 13, 2008, at 08:40 PM


The GTD-TLM looks awesome. Great job. However, like many folks, I don't allow javascript to run in any of my web browsers (especially my cell phone). Is it possible to have the GTD-TLM functionality without any javascript at all? --Ian MacGregor

Thanks! The major GTD-TLM functionality is its speed and responsiveness. It was written in JavaScript in order to be fast fast realtime fast. Nobody can wait for a list manager that is slow, and that has to submit a full HTML form and reload a full page, just to change the status of a task to "Done". At least I don't feel such a program would be usable. As this is free software and source code can be reviewed, if no system-critical bugs are found, and you install it on your website, can't you whitelist/enable JavaScript for your own website? If not, there is PmForm that may be able to handle similar, server based features, if someone codes them (no right-, middle-, shift-, ctrl- click features though). --Petko June 14, 2008, at 10:51 PM
You make some very good points. It doesn't hurt anything to enable javascript (NoScript can do this easily) on the site in which I will run GTD-TLM, good idea. Thanks for writing this great recipe! --Ian MacGregor

Farm installation

Hi, I'm looking at recipe and it seems very cool. It's nice with the fast responses. Anyway, as I installed it I noticed that it uses $PubDirUrl or something like that when for instance locating the .js-file. This is relevant when you've got a farm instalation and want to put the .js-file in the farm's pub dir. /Christian Ridderström

You are probably right, and it should search in $FarmPubDirUrl instead of $PubDirUrl. On most installations it is the same, otherwise, farm fields don't need to run a separate copy of the gtd-tlm.js file. Changed in a new version (just released). --Petko July 10, 2008, at 07:14 AM
A related problem is the location of 'local.css'. Some users may find that their system searches for local.css in $PubDirUrl/css. This should probably be documented in the recipe page. See the page PathVariables. This behaviour might be correct btw. Cheers, /Christian
I feel that this is not a problem; a user will place the CSS code in his usual "local.css" file, or in any css file that is loaded by the skin, the wikigroup or the core. The recipe does not impose the location of the css code. --Petko July 10, 2008, at 10:18 AM

Multiple edits / simultaneous access

Do you know that if two or more browsers access the same list, the last one to save changes will overwrite previous changes? In other words, if I use browser A to modify the list but forgets to save, and then use browser B to save an item, the addition from browser B will be overwritten once I save the changes using browser A.

Yes, I do. Do not edit the same list with two open browsers at the same time :-). The entries from the previous sessions should be found in the Page-gtddata history. I'm investigating if something needs to be changed here and how. --Petko July 10, 2008, at 10:18 AM
I am considering implementing this: if the page was modified in the meantime, all task items from both lists are merged, possibly tagging the changes from the previous session. This way, no information will be lost, even if the user may have for the same task two entries (old and new) if they differed. It is easier to delete a couple of (almost) duplicate entries than to type again some lost ones. Comments? --Petko July 10, 2008, at 10:51 AM

Better View on Tasks

Hi! Is there a possibility to change the view of the tasks a little bit? When there are too many tasks, I easily loose the overview, because the single task-lines don't differ enough. I can see a slight gray line between the tasks, but that's just not enough. Is it possible to make it e. g. black or make more white space between the tasks? I think this would help keeping an overview over your tasks. -- mag 2008-07-22

Yes, in the local CSS file, change the line starting with select.gtd option to something like:
select.gtd option { border-bottom: 1px solid black; padding: .1em 0em; }
The "border" directive sets the width, style and color of the border, and the "padding" sets the distance between the text and the borders (.1em is for top and bottom, 0em for left and right). You can test different paddings with .2em, .3em, etc. Then reload your page in the browser. --Petko July 22, 2008, at 03:04 PM


Hello ! This is a nice work, clap, clap. My question is about the edit rights : is there any way to show the gdt while forbiding any change to non authorized people ? Do one have to put the gtd in a restricted (or out of sight) area to protect him against changes ? Is there an if statement : if authorised -> no limitation vs if non authorised -> view only. Thank you ! gb November 05, 2008, at 12:16 AM

Not built-in, but if your reader has no edit password for your Page-gtddata, a change will not be saved. You could probably use (:if auth edit {*$FullName}-gtddata:) (:gtd-tlm:) (:else:) (:gtd-tlm readonly=1:) (:if:)This will remove the "Save changes" button if the reader cannot save the page. We should probably block all modifications in the edit form in readonly mode, except for searching/filtering. --Petko November 05, 2008, at 02:16 AM

Talk page for the GTD Task List Manager recipe (users).