On 1/30/07, Dfaure <[EMAIL PROTECTED]> wrote: > On 1/30/07, Kathryn Andersen <[EMAIL PROTECTED]> wrote: > > Hi folks! > > > > I'm interested to see if I can use PmWiki for a sort of daily TODO list, > > and neither of the two ToDo recipes do what I want. > > > > http://www.pmwiki.org/wiki/Cookbook/VerySimpleToDo > > is too simple > > > > http://www.pmwiki.org/wiki/Cookbook/ToDo > > is too... complicated... > > > > So I guess I'll have to roll my own, but I have no real idea where to > > start. > > > <grind>Caution, you'll soon to hit our ZAP-man</grind>
I don't think zap is the answer here as Kathryn wants something simple! :) On the other hand, she might want to look at something I did awhile back, for ideas at least. Also recognizing, it's easier to strip functionality out than add it in... ZAPtasks (at www.fast.st/zaptasks) sets up projects with optional documents in each, has a built in rolodex, weekly & monthly scheduling and a calendar (one time and annual). Task can be assigned to any of these items (with notes), and are all pulled into a table on the home page when one logs in (Guest/test). Fully sortable by simply clicking table headers. It also pulls in the schedule for that day and calendar for that month so it's easy to print out and go. And tasks can be marked completed, viewed when done, and/or reactivated. Warning though, while it works great, it is quite complex and might be a bit challenging to customize. Also, it does store individual tasks in separate tasks group, and as text vars (two of Kathryn's criteria that this approach fails). But how else do you get tasks that are dynamic and sortable? Anything inserted into a page is probably not going to be that flexible... Cheers, Dan PS. Now that I think about it, this project would be much easier if it was redone using Hierarchical Groups... :) _______________________________________________ pmwiki-devel mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-devel
