<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="Link_GettingThingsDone" xml:space="preserve">
    <value>Getting Things Done</value>
  </data>
  <data name="Message_Actions" xml:space="preserve">
    <value>Tasks in the Actions category are items that you can currently act on, there is nothing standing in your way. However, since you will likely have many tasks in this category, you will want to set reasonable Due Dates for each of these items.</value>
  </data>
  <data name="Message_Contacts" xml:space="preserve">
    <value>Tasks may be associated with a contact, but they do not have to be. By default, if you create a task it will be associated with [No Contact], but you can assign it to a contact by editing the task and selecting an item from the Contact dropdown, or you can drag a task from the data grid (or calendar) onto the desired node under Contacts in the tree view.</value>
  </data>
  <data name="Message_Contexts" xml:space="preserve">
    <value>Tasks may be associated with a context, but they do not have to be. Examples of contexts might be 'Home' and 'Work'. By default, if you create a task it will be associated with [No Context], but you can assign it to a context by editing the task and selecting an item from the Context dropdown, or you can drag a task from the data grid (or calendar) onto the desired node under Contexts in the tree view.</value>
  </data>
  <data name="Message_GTDOverview1" xml:space="preserve">
    <value>Task-It is based on a methodology called GTD, which stands for Getting Things Done. The GTD methodology was developed by David Allen. You can find out more about this methodology here:</value>
  </data>
  <data name="Message_GTDOverview2" xml:space="preserve">
    <value>The book to the right will give you a basic overview of GTD. To get started, you can either flip the pages with your mouse, or use your right and left arrow keys to navigate through the pages.</value>
  </data>
  <data name="Message_Inbox" xml:space="preserve">
    <value>The Inbox is a place where you collect all of the tasks that you would like to accomplish. After capturing these items, you should then assign them to one of the following categories.</value>
  </data>
  <data name="Message_Projects" xml:space="preserve">
    <value>Tasks may be associated with a project, but they do not have to be. By default, if you create a task it will be associated with [No Project], but you can assign it to a project by editing the task and selecting an item from the Project dropdown, or you can drag a task from the data grid (or calendar) onto the desired node under Projects in the tree view.</value>
  </data>
  <data name="Message_Reference" xml:space="preserve">
    <value>Tasks in the Reference category are things you want to keep track of, but you are not ready to take an action on them yet.</value>
  </data>
  <data name="Message_Someday" xml:space="preserve">
    <value>Tasks in the Someday category are ones that you'd like to accomplish at some point, but they are not a high priority at this time. Basically, you can think of them as items that are on the back burner.</value>
  </data>
  <data name="Message_Ticklers" xml:space="preserve">
    <value>Tasks in the Ticklers category have some sort of recurrence to them. An example might be a weekly task like 'Log weekly accomplishments'.</value>
  </data>
  <data name="Message_Waiting" xml:space="preserve">
    <value>Tasks in the Waiting category have some sort of dependency that must be resolved before you can move ahead with the task. When this dependency has been resolved, the task can be moved to another category.</value>
  </data>
  <data name="PageTitle_Actions" xml:space="preserve">
    <value>Actions</value>
  </data>
  <data name="PageTitle_Contacts" xml:space="preserve">
    <value>Contacts</value>
  </data>
  <data name="PageTitle_Contexts" xml:space="preserve">
    <value>Contexts</value>
  </data>
  <data name="PageTitle_Inbox" xml:space="preserve">
    <value>Inbox</value>
  </data>
  <data name="PageTitle_Projects" xml:space="preserve">
    <value>Projects</value>
  </data>
  <data name="PageTitle_Reference" xml:space="preserve">
    <value>Reference</value>
  </data>
  <data name="PageTitle_Someday" xml:space="preserve">
    <value>Someday</value>
  </data>
  <data name="PageTitle_Ticklers" xml:space="preserve">
    <value>Ticklers</value>
  </data>
  <data name="PageTitle_Waiting" xml:space="preserve">
    <value>Waiting</value>
  </data>
  <data name="Title_GTDOverview" xml:space="preserve">
    <value>GTD Overview</value>
  </data>
  <data name="Title_TheEnd" xml:space="preserve">
    <value>The End</value>
  </data>
</root>