g'day casi, perhaps I can kill 1 1/2 birds with one stone...(and I'm sorry if this explanation goes too far back, if so, it will be useful for others reading this)
I imagine tiddlers kind of like index cards - each tiddler is one index card that holds one piece of information, whether that be a system setting, a background process, a task, a project, a tickler, etc. The tags that are given to a particular tiddler determine how that tiddler relates to other tiddlers. This is far reaching and powerful, as those tags tell other tiddlers that control how mGSD operates how to handle and display information. For example, simply tagging a tiddler 'F' (without quotes) tells the system tiddlers to display that tiddler as a future item. So, every task in mGSD is tagged 'Action' and every project in mGSD is tagged 'project'. It is the way that mGSD handles tags that makes quick add truly brilliant. If you add a single task as such: *.book flights* then mGSD adds the tags 'Action' and 'Next' to the tiddler. If you made it part of a project like so: *Australia trip .book flights * Then mGSD would create 2 tiddlers: 1 titled 'Australia trip' with the tags 'Project' and 'Active', and 1 titled 'book flights' with the tags 'Action', 'Next', and 'Australia trip'. This last tag of the 2nd tiddler tells mGSD that the tiddler is associated with the 'Australia trip' tiddler, and because one is a project and the other an action, then it makes the one a task that is part of that project. If a tiddler [[tiddler 2]] is tagged with the name of another tiddler [[tiddler 1]], then mGSD works out the relationship between them (as above). So if they are both tagged 'Action', then [[tiddler 2]] is dependent on [[tiddler 1]] and will not be displayed until [[tiddler 1]] is marked (tagged) complete. Likewise, a project tiddler which has a tag which is a project will recognise that one is the subproject of the other. Why is all this important? Because you can tag tiddlers from the quick add when you create them. So this is an example of a complex project you could enter in the quick add: because any dependencies in mGSD work by assigning tags to tiddlers, it would work exactly the same way as putting dependencies into actions. (Also, this is the way that an action can have multiple dependencies - just add the other dependent tasks as tags). *Organise Australia trip|Personal .determine dates|@Home .research 5 cities|@Computer|F|determine dates contact Aussie friends|Personal|Organise Australia trip .email Bruce|@Computer .call Davo|@Calls make bookings|Personal|Organise Australia trip .book return flights home|@Computer .book hotel|@Computer .book car|@Computer .lock in Bruce for day trip to Sydney Harbour|@Computer|F|book hotel|book car* and so on and so forth... anything after a | gets treated as a tag. Just make sure that you've got each of the task dependencies tagged with |F| to show that they are future. This way very precise (much more so than any other GTD system that I've looked at) action sequences can be articulated and won't be displayed until they can be done. hope this extended answer helps -- You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/gtd-tiddlywiki/-/BRFyw9GIsvAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
