Getting Things Done On WikidPad

A Snazzy System for Getting Things Done using the desktop program wikidPad for Windows

Introduction

GTD_NA_view.jpg

wikidPad is a desktop wiki for windows which uses plain text for data and Python under the bonnet. Its special trick is an ingenious dynamically generated outline view. There is no page heirarchy implied or created by the outline; it is simply a representation of the linking system. There are formatting tricks which you can utilise for tagging the pages and displaying them as lists in the outline. Here you will get a quick idea of how set up a useful GTD system using these tags.

This tutorial assumes you know a little about wikis and about using camelcase words.

First, download the program. Take a look at the help wiki if you like, but it's not necessary for the purposes of this tutorial; you can just follow my super-quick orientation. (Just bear in mind, if you are used to wikis, that there is no separate edit and view modes; the text formatting is always visible.)

Super quick wikidPad orientation


todo.email:Jo about keys

[Current:this week]



todo.home:mend chair leg

[complete:041229]

(The uppercase C in Current is a hack to make it appear at the top of the outline list.

Using keywords and attributes

So you've seen how you can make pages show up in different places in the tree. You're going to be applying this to generate lists of contexted next actions with markers for project status, such as current, somedaymaybe, tickler and complete. The next actions are all going to show up in a list sorted by context, but you will be able to distinguish between current and tickler projects by their colour. How you will do this is by creating a page per project, and then writing your next actions and status markers in such a way to show up usefully in the tree. This is acheieved by using keywords and attributes, and here is an explanation of the difference between them and how they can be used.

Keywords

Attributes


Applying this to your wiki

To create your useful status colour-coding; write the following on any page (or use the wiki settings page for neatness):

[global.Current.this week.color:lime green]

[global.complete.color:light grey]

You can see where we're going now, I am sure, and to start you off here are some default attributes and their settings (note where to put the periods and the colons):

[Current:urgent]

[Current:this week]

[someday:maybe]

[tickler:date in sortable format here]

[complete:completion date here]



[global.Current.urgent.color:red]

[global.Current.this week.color:lime green]

[global.someday.color:dim grey]

[global.tickler.color:grey]

[global.complete.color:light grey]

So now you can start entering your next actions, using the todo keyword syntax, and annotating your project pages with the attribute syntax.

GTD_Tickler_view.jpg