A Tinderbox Toolshed
The Front Door
There's No Place Like Home
GTD-Take it From the Top
Quick Notes
About Me
About ProtoTyping
Recent Notes
Put in a New Context - Part III - Project and Actions Setup
Put in a New Context - Part II - The Agent
Put in a New Context - Part I - The Prototype
A Picture's Worth a Thousand Words
The Workbench
Read More of the Story? Click here!
Read More of the Story II: The Templates
My ToDo List
The Storage Shed
The Junkdrawer
A System for Success
Attributes are the detailed features of each note; everything from the color of the note to how a note will affect it's parents, sibling and children. Many of the key attributes are visible for each note in Explorer View. That visibility is controlled overall by the system attribute called KeyAttributes as well as by the selection of attributes for individual notes using the pulldown within the note region above the scrollbar.
Several system attributes are essential for GTD and are important in the Creation, and Input or Processing phase of the daily or weekly review. Creation is the customization you will do to transform this tool to meet your needs and Input is the daily or weekly management of projects and actions. Input and Processing is the construction of specific action items for a given project.
As an aside, remember, creation and input should be discreet and separate from the doing. It's all too easy to fall into the tinkering trap. This should be done during a daily or weekly Review that you schedule with a Repeating note in @Office.
System attributes include settings useful for the construction of new locations or Contexts. These contexts are assigned using a system attribute called Prototype. For the note which is the prototype note for a given context, such as *Office or *Darkroom, the attribute IsPrototype is set to true. This attribute is what allows Agents to collect and sort notes by context through a search that collects all notes which are linked to specific prototype notes. Those links are achieved through another system attribute called Prototype, where the name of the prototype note is supplied.
The organization and assignment of Contexts takes place in the main body of the outline. For instance, it is where @Office and @Darkroom will assign the appropriate prototype to new child notes through another key system attribute called OnAdd. OnAdd sets the Prototype attribute for the added note to reflect the appropriate context reflected by the parent of the new child.
In addition, now in Tinderbox 2.4 the newly added note may act on its parent, siblings or children through a new attribute called Rule. In other words, a note can act on other notes much as OnAdd, but in the reverse direction and, in some cases, with continuous effect.
The power that is built into Tinderbox derives in large part from the power of the attributes. Attributes add a critical dimension to the multidimensional world that is Tinderbox. Understanding how attributes work is one of the keys to harnessing that power.
A Shed with a View
Tinderbox Help
GTD on the Web
My Toolbox
The Bookshelf
Leaving a Trace: On Keeping a Journal
Tinderbox
