Merge lp:~gtg-contributors/gtg/bugfix-629683 into lp:~gtg/gtg/old-trunk

[Bertrand Rousseau]

Update the initial tutorial for 0.3. As no many specific themes were listed in the bug description (see https://bugs.launchpad.net/gtg/+bug/629683). It's merely a rephrasing/reorganization of the text.

[Izidor Matušov (izidor)]

I suggest that this is the final patch for the bug and afterwards it will be marked as fixed. In other words, nitpicking is appropriate :)

You sometimes use normal quotes instead of xml entity ", e.g. "save" button. We should stick to a consistent style. Foot note: normal quotes works in the same way as xml entity " Maybe use normal quotes?

I think we should promote our blog http://gtg.fritalk.com as well in initial tutorial. (after link to launchpad) Something like "If you want to get tips for using GTG or be informed about the newest features, visit our blog at http://gtg.fritalk.com"

"Sometimes it is easier to cut down a task in several smaller tasks. GTG helps to do just this by defining "subtasks". In GTG, those subtasks are prerequisite that must be completed before being able to close their parent task."

If I recall correctly, the correct definition of subtasks in GTG is more about prerequisites than a smaller tasks which happens to have the same parent. <this is more brainstorming than nitpicking>

"Note that subtasks obey to some rules: first, a subtask's due date can never be happen after its parent's due date and, second, when you mark a parent task as done, its subtasks will also be marked as done."

<brainstorming>There is no mention for the rule start_date < due_date.</brainstorming>

I would also formulate when you close a parent task, its subtasks will be closed as well" (It is true for dismissing or deleting tasks)

The tasks that you marked as done or dismissed are stored in the Closed Tasks Pane which is hidden by default, but you can easily enable it using the View menu.

<brainstorming>Use instead exact menu path? View -> Closed tasks pane</brainstorming>

" Here are other stuff you will find interesting to read:"

It sounds strange to me although I am not a native speaker. Maybe "There is other stuff you will find interesting to read" or even "There is even more to discover:"

"If you right click on a tag in the sidebar you can also set its color. It will allow you to have a more colorful list of tasks, if you want it that way."

<brainstorming>We should propagate your awesome tag editor. What do you say?</brainstorming>

Could you please use suggestions from bug #615027? Better suggest the new user tags for keeping "hierarchy"

There is a missing condition in WorkView to hide a task: set due date to "someday" to hide ideas which needs more thoughts

"If you use tags, you can right click on a tag in the sidebar and choose to hide tasks assigned to this particular tag in the workview. It's very useful if you have a tag like "someday" that you use for tasks you would like to do but are not particularly urgent."

This paragraph could be updated to use another example, e.g. @wait when you wait for a response from your teammate.

It might help to stress that tasks are hidden immediately, i.e. when you drag-and-drop a subtask to another task, the parent is hidden. Or when you trigger another condition. We should prepare user for that "wow" effect when tasks are hidden in real time and suggest turning off Workview when planing for a next week or so.

"Some examples of the current plugins are synchronization with o...

review: Approve (code, running)

[Izidor Matušov (izidor)]

The correct status should be "Needs Fixing"

review: Needs Fixing (code, running)

[Bertrand Rousseau (bertrand-rousseau)]

Thanks for the remarks Izidor, I'll try to include most of them. I answered
in the text.

First as a general note, I think it's important to make it clear that those
tutorial tasks are not meant to tell everything about GTG. The goal is to
get a first insight on how GTG works. So when I edited those tasks, I
didn't try to cover everything, hence there are some aspects lacking on
purpose.

On Wed, Jul 18, 2012 at 9:59 PM, Izidor Matušov <email address hidden>wrote:

> Review: Approve code, running
>
> I suggest that this is the final patch for the bug and afterwards it will
> be marked as fixed. In other words, nitpicking is appropriate :)
>
> You sometimes use normal quotes instead of xml entity &quot;, e.g. "save"
> button. We should stick to a consistent style. Foot note: normal quotes
> works in the same way as xml entity &quot; Maybe use normal quotes?
>

&quot; was used when I edited the tasks. Maybe I forgot to convert some. To
guarantee 100% compatibility with XML, I'll stick to &quot;

> I think we should promote our blog http://gtg.fritalk.com as well in
> initial tutorial. (after link to launchpad) Something like "If you want to
> get tips for using GTG or be informed about the newest features, visit our
> blog at http://gtg.fritalk.com"
>

Ok, I agree.

> "Sometimes it is easier to cut down a task in several smaller tasks. GTG
> helps to do just this by defining "subtasks". In GTG, those subtasks are
> prerequisite that must be completed before being able to close their parent
> task."
>
> If I recall correctly, the correct definition of subtasks in GTG is more
> about prerequisites than a smaller tasks which happens to have the same
> parent. <this is more brainstorming than nitpicking>
>

Yes, but the general idea is to define "smaller" (a.k.a. more operational
tasks) to help you actually progress in your work and in that definition,
smaller tasks are actually prerequisites to a bigger tasks. I could put
more emphasis on that nuance in the text (but the idea here is not to teach
people how to organize themselve, it's not GTG's purpose).

> "Note that subtasks obey to some rules: first, a subtask's due date can
> never be happen after its parent's due date and, second, when you mark a
> parent task as done, its subtasks will also be marked as done."
>
> <brainstorming>There is no mention for the rule start_date <
> due_date.</brainstorming>
>

I'm not sure I will make that explicit. It's kind of obvious, or at least
it could be easily understood by someone experiencing the effect of the
rule.

> I would also formulate when you close a parent task, its subtasks will be
> closed as well" (It is true for dismissing or deleting tasks)
>

I think it's explained somewhere, but I'll check. This must be clear,
indeed.

The tasks that you marked as done or dismissed are stored in the Closed
> Tasks Pane which is hidden by default, but you can easily enable it using
> the View menu.
>
> <brainstorming>Use instead exact menu path? View -> Closed tasks
> pane</brainstorming>
>

I think I'll pass on that one, I prefer not using a complex syntax.

> " Here are other stuff you will find interesting to read:"
>
> It sounds strange to me ...

[lp:~gtg-contributors/gtg/bugfix-629683]

1211. By Bertrand Rousseau on 2012-07-20

Update the first tutorial task

1212. By Bertrand Rousseau on 2012-07-20

Updated all actual first run tasks

1213. By Bertrand Rousseau on 2012-07-20

Fixes for bugs: update tutorial, add tutorial tasks for sync. services and saved searches.

1214. By Bertrand Rousseau on 2012-07-20

Merge trunk

1215. By Bertrand Rousseau on 2012-07-20

Also add mallard documentation pages for the search feature.

[Bertrand Rousseau (bertrand-rousseau)]

Hi,

I updated the initial tutorial tasks to take your remarks into account. I also added two tasks: one for the search feature, on for the synchronization services. I also added mallard pages for the search feature. Please review and tell me if you have remarks regarding the text.

[Izidor Matušov (izidor)]

Hi Bertrand,

nice job! I still have few remarks:

There is still a link to https://bugs.launchpad.net/gtg instead of https://bugs.launchpad.net/gtg/+filebug It would make eliminate one step of reporting bug - loading a database of bugs and finding "Report bug" link. The links occurs 2 times: the main task and "Report bugs" task.

In how task "Learn how to search for tasks" you should mention it is possible to search by parameters of tasks as well (maybe give an example like @errands !today - errands to be done today) and refer to help for more details.

I made a typo in the original search documentation in "Show GTG tasks with due_date before Marz 1" where it should be March 1 instead of Marz 1. Could you please correct it both in original comment and documentation? Thank you.

review: Needs Fixing (code, running)

[lp:~gtg-contributors/gtg/bugfix-629683]

1216. By Bertrand Rousseau on 2012-07-22

Fixes remarks from Izidor's review

[Bertrand Rousseau (bertrand-rousseau)]

Done, done, and done!

On Sun, Jul 22, 2012 at 2:24 PM, Izidor Matušov <email address hidden>wrote:

> Review: Needs Fixing code, running
>
> Hi Bertrand,
>
> nice job! I still have few remarks:
>
> There is still a link to https://bugs.launchpad.net/gtg instead of
> https://bugs.launchpad.net/gtg/+filebug It would make eliminate one step
> of reporting bug - loading a database of bugs and finding "Report bug"
> link. The links occurs 2 times: the main task and "Report bugs" task.
>
> In how task "Learn how to search for tasks" you should mention it is
> possible to search by parameters of tasks as well (maybe give an example
> like @errands !today - errands to be done today) and refer to help for more
> details.
>
> I made a typo in the original search documentation in "Show GTG tasks with
> due_date before Marz 1" where it should be March 1 instead of Marz 1. Could
> you please correct it both in original comment and documentation? Thank you.
>
>
> --
>
> https://code.launchpad.net/~gtg-contributors/gtg/bugfix-629683/+merge/115353<https://code.launchpad.net/%7Egtg-contributors/gtg/bugfix-629683/+merge/115353>
> You proposed lp:~gtg-contributors/gtg/bugfix-629683 for merging.
>

--
Bertrand Rousseau

[lp:~gtg-contributors/gtg/bugfix-629683]

1217. By Bertrand Rousseau on 2012-07-22

Merge trunk, fixes CHANGELOG conflict

[Izidor Matušov (izidor)]

Thanks for good job!

review: Approve

=== modified file 'CHANGELOG'
--- CHANGELOG	2012-07-20 09:46:12 +0000
+++ CHANGELOG	2012-07-22 18:10:24 +0000
@@ -32,6 +32,9 @@
     * Fixes for bugs #906516, #1002160 (task urgency color plugin), by Wolter Hellmund
     * Fix for bug #1001012: Notification area icon should change color when there are urgent tasks, by Antonio Roquentin
     * Saner implementation of set_due_date
+    * Fix for bug #629683: update initial tutorial for 0.3
+    * Fix for bug #615027: Introductory task set should suggest organizing tasks in a tag hierarchy
+    * Fix for bug #1026264: Write user documentation for search/smart tag
 
 2012-02-13 Getting Things GNOME! 0.2.9
     * Big refractorization of code, now using liblarch

=== modified file 'GTG/core/firstrun_tasks.py'
--- GTG/core/firstrun_tasks.py	2012-05-23 08:55:31 +0000
+++ GTG/core/firstrun_tasks.py	2012-07-22 18:10:24 +0000
@@ -27,137 +27,321 @@
 
 
 def populate():
+    """On the first run of GTG, populate the task list with tasks meant to
+    act as a GTG tutorial."""
     doc, root = cleanxml.emptydoc("project")
 
     #Task 0@1: Getting started with GTG
-    title1 = _("Getting started with GTG")
-    text1 = _("""Welcome to Getting Things Gnome!, your new task manager.
-
-In GTG, everything is a task. From building a bridge over the Pacific Ocean to changing a light bulb or organizing a party. Task is automatically saved while you are editing.
-
-Once you are done with a specific task, you can push the "Mark as Done" button. If the task is not relevant anymore, simply press "Dismiss" button.
-
-A task might be composed of multiple subtasks that appear as links in the task description. Simply click on the following link to open the subtask:""")
-    text1 += "\n<subtask>1@1</subtask>\n"
-    text1 += _("""Once you've read the above subtask, mark it as done. If you don't want to do the task, mark it as dismissed. Tasks that you marked as done or dismissed are stored in the Closed Tasks Pane which is hidden by default, but you can easily enable it in the View menu.
-    
-If you choose to close this current task, subtasks will be automatically closed too. GTG considers that if you have completed a given task, you don't need to do the subtasks anymore.
-
-Other stuff you should read:""")
-    text1 += """\n<subtask>2@1</subtask>
-    <subtask>3@1</subtask>
-    <subtask>4@1</subtask>
-    <subtask>5@1</subtask>
-    <subtask>6@1</subtask>\n"""
-    text1 += _("""We hope that you will appreciate GTG. Please send us bug reports and ideas for improvement using:
-    https://bugs.launchpad.net/gtg
-
-Thank you for trying out GTG :-)""")
-    t1 = addtask(doc, "0@1", title1, text1, ["1@1", "2@1", "3@1", "4@1", "5@1", "6@1"])
-    root.appendChild(t1)
+    title1 = _("Getting Started With GTG")
+    text1 = _(\
+"Welcome to Getting Things GNOME!, your new task manager! In Getting "
+"Things GNOME! (GTG), everything is a task. From building a bridge over "
+"the Pacific Ocean to changing a light bulb or organizing a party!\n"
+"\n"
+"If you are new to GTG, please take the time to read this, as it will "
+"provide you useful information about how to use GTG to organize your "
+"everyday life.\n"
+"\n"
+"Creating and editing tasks:\n"
+"\n"
+"Using GTG is easy: you organize what you have to do by creating new "
+"tasks. To do this, simply press the &quot;New Task&quot; button, "
+"edit the task by describing it, set some parameters, and that's "
+"it! Once a task done, you can close it by pressing the &quot;Mark As "
+"Done&quot; button.\n"
+"\n"
+"In GTG, a task is automatically saved while you are editing it. No need to "
+"press any &quot;Save&quot; button! Try it: add some text to this task, close "
+"the window, and reopen it: your changes are still there!\n"
+"\n"
+"About subtasks:\n"
+"\n"
+"In life, you often get more things done by refining them in "
+"smaller, more operational tasks. GTG helps to do just this by defining "
+"&quot;subtasks&quot;. In GTG, those subtasks are considered as prerequisites "
+"that must be completed before being able to close their parent task.\n"
+"\n"
+"Therefore, in GTG, a task might host one or several subtasks. Those "
+"appear as links in the task description, just like the link below. To "
+"open and edit a subtask, simply click on its link! Try it yourself: open "
+"the following subtask:\n"
+"<subtask>1@1</subtask>\n"
+"\n"
+"Closing a task:\n"
+"\n"
+"In GTG, once you are done with a task, you can close it by pushing "
+"either the &quot;Mark as Done&quot; or the &quot;Dismiss&quot; button. "
+"Use the first one if the task is done, and the latter if you want to "
+"close it because it is not relevant anymore. Want to try it? Try to "
+"close the subtask above for instance!\n"
+"\n"
+"When you close a task, you will notice that all its subtasks will be "
+"automatically closed too! Indeed, GTG considers that if you have completed a "
+"given task, then you don't need to do its subtasks anymore (they were "
+"prerequisites, after all).\n"
+"\n"
+"Note that the tasks that you have marked as done or dismissed are listed in "
+"the &quot;Closed Tasks Pane&quot; which is hidden by default, but you can "
+"easily show it using the View menu.\n"
+"\n"""
+"Learn more about GTG:\n"
+"\n"
+"If you are interested in knowing more about "
+"GTG's other features, you will find more information here:\n"
+"<subtask>2@1</subtask>\n"
+"<subtask>3@1</subtask>\n"
+"<subtask>4@1</subtask>\n"
+"<subtask>5@1</subtask>\n"
+"<subtask>6@1</subtask>\n"
+"<subtask>7@1</subtask>\n"
+"<subtask>8@1</subtask>\n"
+"\n"
+"You can also browse GTG documentation by pressing F1 or opening it using "
+"the Help menu.\n"
+"\n"
+"We sincerely hope you will enjoy using GTG, and thank you for trying it out! "
+"Please send us bug reports and ideas for improvement using this web page: "
+"https://bugs.launchpad.net/gtg/+filebug If you want to get tips for using "
+"GTG or be informed about the newest features, also visit our blog at "
+"http://gtg.fritalk.com\n"
+"\n"
+"The GTG team.")
+    task1 = addtask(doc, "0@1", title1, text1, \
+        ["1@1", "2@1", "3@1", "4@1", "5@1", "6@1", "7@1", "8@1"])
+    root.appendChild(task1)
 
     #Task 1@1: Learn to use subtasks
-    title2 = _("Learn how to use subtasks")
-    text2 = _("""&quot;Subtask&quot; is something that you need to do first in order to accomplish your task. To insert a subtask in the task description (this window), begin a line with &quot;-&quot;, write the subtask title and press Enter. Try inserting one subtask below.
-    
-You can also use the &quot;insert subtask&quot; button.
-
-Tasks and subtasks can be re-organized by drag-n-drop in the tasks list.
-
-Subtasks have certain rules: for example, a subtask's due date can never be after its parent's due date and when you mark a parent task as done, its subtasks will also be marked as done.""")
-    t2 = addtask(doc, "1@1", title2, text2, [])
-    root.appendChild(t2)
+    title2 = _("Learn How To Use Subtasks")
+    text2 = _(\
+"A &quot;Subtask&quot; is something that you need to do first before being "
+"able to accomplish your task. In GTG, the purpose of subtasks is to cut down "
+"a task in smaller subtasks that are easier to achieve and to track down.\n"
+"\n"
+"To insert a subtask in the task description (this window, for instance), "
+"begin a line with &quot;-&quot;, then write the subtask title and press "
+"Enter.\n"
+"\n"
+"Try inserting one subtask below. Type &quot;- This is my first "
+"subtask!&quot;, for instance, and press Enter:\n"
+"\n"
+"\n"
+"\n"
+"Alternatively, you can also use the &quot;Insert Subtask&quot; button.\n"
+"\n"
+"Note that subtasks obey to some rules: first, a subtask's due date can never "
+"happen after its parent's due date and, second, when you mark a parent "
+"task as done, its subtasks will also be marked as done.\n"
+"\n"
+"And if you are not happy with your current tasks/subtasks organization, you "
+"can always change it by drag-and-dropping tasks on each other in the tasks "
+"list.")
+    task2 = addtask(doc, "1@1", title2, text2, [])
+    root.appendChild(task2)
 
     #Task 2@1: Learn to use tags
-    title3 = _("Learn how to use tags")
-    text3 = _("""A tag is a simple word that begins with &quot;@&quot;.
-
-Try to type a word beginning with @ here:
-
-It becomes yellow, it's a tag.
-
-Tags are useful to sort your tasks. In the view menu, you can enable a sidebar which displays all the tags you are using so you can easily see tasks assigned to a given tag. There's no limit to the number of tags a task can have.
-
-You can drag-n-drop a tag onto another to create \"subtags\". As an example, if you drag the tag @to_pay onto the tag @money, every task tagged with @to_pay will also appear in the view of @money (but the @money tag is not added to the task).
-
-If you right click on a tag in the sidebar you can also set its color. It will allow you to have a more colorful list of tasks, if you want it that way.
-
-A new tag is only added to the current task. There's no recursion and the tag is not applied to subtasks. But when you create a new subtask, this subtask will inherit the tags of its parent as a good primary default (it will also be the case if you add a tag to a parent just after creating a subtask). Of course, you can modify at any time the tags of this particular subtask. It will never be changed by the parent.""")
-    t3 = addtask(doc, "2@1", title3, text3, [])
-    root.appendChild(t3)
+    title3 = _("Learn How To Use Tags")
+    text3 = _(\
+"In GTG, you use tags to sort your tasks. A tag is a simple word that begins "
+"with &quot;&#64;&quot;.\n"
+"\n"
+"Try to type a word beginning with &quot;&#64;&quot; here:\n"
+"\n"
+"Once it becomes yellow, it is a tag! And this tag is now linked to the "
+"task!\n"
+"\n"
+"Using the View menu, you can enable a sidebar which displays all the tags "
+"you are using. This allows you to easily see all tasks associated to a "
+"given tag.\n"
+"\n"
+"If you right-click on a tag in the sidebar, you can also edit it. It allows "
+"you to assign it a color or an icon for instance. This is handy if you want "
+"to quickly identify the tasks associated to a given tag in the task list!\n"
+"\n"
+"New tags are always added exclusively to the currently edited task, and "
+"never to its subtasks. However, when you create a new subtask, it will "
+"inherit its parent's tags.\n"
+"\n"
+"If you need a more advanced task organization, you can also create a "
+"hierarchy of tags by drag-and-dropping a tag onto another. This is useful "
+"when you want to regroup several tags together and see all related tasks "
+"easily. For instance, if you have two tags &#64;money and &#64;to_pay, and "
+"you drag &#64;to_pay on &#64;money, every task tagged with &#64;to_pay will "
+"also appear when you select &#64;money.")
+    task3 = addtask(doc, "2@1", title3, text3, [])
+    root.appendChild(task3)
 
     #Task 3@1: Using the Workview
-    title4 = _("Learn how to use the Workview")
-    text4 = _("""If you press the &quot;Workview&quot; button, only actionable tasks will be displayed.
-
-What is an actionable task? It's a task you can do directly, right now.
-
-It's a task that is already &quot;start-able&quot;, i.e. the start date is already over.
-
-It's a task that doesn't have open subtasks, i.e. you can do the task itself directly.
-
-Thus, the workview will only show you tasks you should do right now.
-
-If you use tags, you can right click on a tag in the sidebar and choose to hide tasks assigned to this particular tag in the workview. It's very useful if you have a tag like &quot;someday&quot; that you use for tasks you would like to do but are not particularly urgent.""")
-    t4 = addtask(doc, "3@1", title4, text4, [])
-    root.appendChild(t4)
+    title4 = _("Learn How To Use The Work View")
+    text4 = _(\
+"If you press the &quot;Work View&quot; button, only actionable tasks will "
+"be displayed in your list.\n"
+"\n"
+"What is an actionable task? It's a task you can do directly, right now.\n"
+"\n"
+"It's a task that is already &quot;start-able&quot;, i.e. the start date "
+"is already over.\n"
+"\n"
+"It's a task that doesn't have open subtasks, i.e. you can do the task "
+"itself directly.\n"
+"\n"
+"It's a task that has a due date different than &quot;Someday&quot;, since "
+"this kind of date is reserved for things that needs more thoughts before "
+"being actionable.\n"
+"\n"
+"Thus, in short, the Work View shows you tasks that you can do right now. "
+"It's very useful when you want to get things done and to focus on the "
+"relevant tasks!\n"
+"\n"
+"If you use tags, you can right click on a tag in the sidebar and choose "
+"to hide tasks assigned to this particular tag in the Work View. It is very "
+"useful if you have a tag like &quot;&#64;wait&quot; that you use for tasks "
+"blocked by some external event (i.e. a phone call you wait to receive).\n"
+"\n"
+"And finally, an important note regarding the Work View: since the Work View "
+"is updated instantaneously, if you edit your task while using the Work "
+"View, this task might disappear due to the change you just made (e.g. "
+"adding a subtask, adding a tag hidden in the Work View, etc.). To avoid "
+"this, it's better not to edit your task while using the Work View.")
+    task4 = addtask(doc, "3@1", title4, text4, [])
+    root.appendChild(task4)
 
     #Task 5@1: Plugins
-    title5 = _("Learn how to use Plugins")
-    text5 = _("""GTG has the ability to add plugins to extend it's core functionality.
-
-Some examples of the current plugins are Syncing with Remember the Milk and Evolution, Tomboy/Gnote integration and Geolocalized Tasks.
-You can find the Plugin Manager by selecting Edit in the Menu Bar, then clicking Preferences. You will then see a tab labeled Plugins.""")
-
-    t5 = addtask(doc, "4@1", title5, text5, [])
-    root.appendChild(t5)
+    title5 = _("Learn How To Use Plugins")
+    text5 = _(\
+"GTG has the ability to add plugins to extend its core functionality.\n"
+"\n"
+"Some examples of the currently available plugins are the notification "
+"icon which displays a handy shortcut to GTG in your notification space, or "
+"the closed tasks remover which automatically deletes old tasks from your "
+"closed tasks list.\n"
+"\n"
+"You can find the Plugin Manager by selecting Edit in the Menu Bar, then "
+"clicking Plugins.")
+    task5 = addtask(doc, "4@1", title5, text5, [])
+    root.appendChild(task5)
 
     #Task 5@1: Reporting bugs
-    title6 = _("Reporting bugs")
-    text6 = _("""GTG is still very alpha software. We like it and use it everyday but you will encounter some bugs.
-
-Please, report them on our Launchpad page:
-https://bugs.launchpad.net/gtg
-
-We need you to make this software better. Any contribution, any idea is welcome.
-
-If you have some trouble with GTG, we might be able to help you or to solve your problem really quickly.""")
-
-    t6 = addtask(doc, "5@1", title6, text6, [])
-    root.appendChild(t6)
+    title6 = _("Reporting Bugs")
+    text6 = _(\
+"GTG is still beta software. We like it and use it everyday but you will "
+"probably encounter some bugs will you do.\n"
+"\n"
+"Please, help us improving GTG by reporting them on our Launchpad page:"
+"https://bugs.launchpad.net/gtg/+filebug\n"
+"\n"
+"We need you to make this software better. Any contribution, any idea is "
+"welcome!\n"
+"\n"
+"If you have some trouble with GTG, we might be able to help you or to "
+"solve your problem really quickly.")
+    task6 = addtask(doc, "5@1", title6, text6, [])
+    root.appendChild(task6)
 
     #Task 6@1: Learn how to use the QuickAdd Entry
-    title7 = _("Learn how to use the Quick Add Entry")
-    text7 = _("""The Quick Add Entry is the fastest way to create a new task. Use the check box in the View menu to enable and disable the entry field.
-
-To add a task simply type its title in the entry and press Enter. The task will be created and selected in the task browser. If a tag is selected in the Tags Sidebar, it will be applied to the task you created.
-
-You can also create a task in the Quick Add Entry and at the same time specify its tags, due and defer date. Follow these format rules:
-
-
-tags:tag1,tag2,tag3
- - This way you can apply as many tags as you wish using comma as separator
- - Any word that begins with &quot;@&quot; will be interpreted as a tag
-
-due:date
-defer:date
- - This way you can apply a due date or a defer date. Dates can be formated as yyyy-mm-dd (for example 2012-04-01) or yyyymmdd (20120401) or mmdd (0401 - the year being implicitly the current one) or today, tomorrow or a weekday name (due:monday means due next Monday). Dates which are added in this way will not appear in the task title.
-
-Examples:
-buy stationary tags:purchases,office due:20120330 defer:tuesday
-
- - The above example tells GTG to create a new task with the title "buy stationary", under the tags "purchases" and "office", with the due date March 30, 2012 and the start date next Tuesday.
-
-call mum tags:family,calls due:sunday defer:tomorrow
- - The above example tells GTG to create a new task with the title "call mum", under the tags "family" and "calls", with the due date next Sunday and the start date tomorrow.""")
-
-    t7 = addtask(doc, "6@1", title7, text7, [])
-    root.appendChild(t7)
+    title7 = _("Learn How To Use The Quick Add Entry")
+    text7 = _(\
+"The Quick Add Entry is the fastest way to create a new task. Use the check "
+"box in the View menu to enable and disable the entry field.\n"
+"\n"
+"To add a task simply type its title in the entry and press Enter. The task "
+"will be created and selected in the task browser. If a tag is selected in "
+"the Tags Sidebar, it will be applied to the task you created.\n"
+"\n"
+"You can also create a task in the Quick Add Entry and at the same time "
+"specify its tags, due and defer date. Follow these format rules:\n"
+"\n"
+"tags:tag1,tag2,tag3\n"
+"\n"
+"Using this you can apply as many tags as you wish using comma as "
+"separator. Note that any word in the title that begins with &quot;@&quot; "
+"will also be interpreted as a tag!\n"
+"\n"
+"due:date\n"
+"defer:date\n"
+"\n"
+"Using this you can apply a due date or a defer date. Dates can be "
+"formated as yyyy-mm-dd (for example 2012-04-01) or yyyymmdd (20120401) "
+"or mmdd (0401 - the year being implicitly the current one) or today, "
+"tomorrow or a weekday name (due:monday means due next Monday). Dates "
+"which are added in this way will not appear in the task title.\n"
+"\n"
+"Examples:\n"
+"\n"
+"buy stationary tags:purchases,office due:20120330 defer:tuesday\n"
+"\n"
+"The above example tells GTG to create a new task with the title "
+"&quot;buy stationary&quot;, under the tags &quot;purchases&quot; and "
+"&quot;office&quot;, with the due date March 30, 2012 and the start date "
+"next Tuesday.\n"
+"\n"
+"call mum tags:family,calls due:sunday defer:tomorrow\n"
+"\n"
+"The above example tells GTG to create a new task with the title "
+"&quot;call mum&quot;, under the tags &quot;family&quot; and "
+"&quot;calls&quot;, with the due date next Sunday and the start date "
+"tomorrow.")
+    task7 = addtask(doc, "6@1", title7, text7, [])
+    root.appendChild(task7)
+
+    #Task 7@1: Learn How To Use Synchonization Services
+    title8 = _("Learn How To Use Synchronization Services")
+    text8 = _(\
+"Synchronization Services allow GTG to synchronize (meaning to have access "
+"or to import) tasks, notes or bugs from other sites or services like "
+"Launchpad, Remember the Milk, Tomboy, etc.\n"
+"\n"
+"This can incredibly useful if, for instance, you want to access your tasks "
+"on several instances of GTG running on separate computers, or if you want "
+"to edit your tasks using an online service. GTG can also import tasks from "
+"specific sites like launchpad for instance, which allows you "
+"to manage the bug reports you're working on in GTG!\n"
+"\n"
+"To use Synchronization Services, use the Edit menu, and select "
+"&quot;Synchronization Services&quot;. You will then have the possibility "
+"to select among several online or local services from/to where you can "
+"import or export your tasks.\n"
+"\n"
+"If you want to know more about Synchronization Services, you can read "
+"more about them by in the dedicated documentation in GTG's help (use "
+"the Help menu or press F1 to get access to it).")
+    task8 = addtask(doc, "7@1", title8, text8, [])
+    root.appendChild(task8)
+
+    #Task 8@1: Learn How To Search For Tasks
+    title9 = _("Learn How To Search For Tasks")
+    text9 = _(\
+"To help you to find specific tasks more easily, GTG allows you to search "
+"for tasks based on their content.\n"
+"\n"
+"Searching for tasks is really easy: just type the words you are looking for "
+"in the Quick Add Entry, and select &quot;Search&quot; in the menu that "
+"will appear automatically.\n"
+"\n"
+"GTG stores your searches in the sidebar, under the &quot;Search&quot; "
+"section. You can thus always go back to a previous search later on if you "
+"need it. Search results are updated automatically, so you always get "
+"all the tasks matching your search request.\n"
+"\n"
+"GTG also saves all the search requests you have made until you explicitely "
+"delete them (which you can do by right-clicking on them and selecting "
+"&quot;Delete&quot;). That allows you to safely quit GTG without loosing your "
+"search requests. This can be very useful when you use the search features "
+"to identify specific tasks regularly!\n"
+"\n"
+"GTG search feature is really powerful and accept many parameters that "
+"allows you to search for very specific tasks. For instance, using the search "
+"query &quot;&#64;errands !today&quot;, you can search for tasks with the "
+"&#64;errands tag that must be done today. To learn more about those search "
+"query parameters, you can read the documentation available in GTG's help "
+"(press F1 or use the Help menu to get access to it).")
+    task9 = addtask(doc, "8@1", title9, text9, [])
+    root.appendChild(task9)
 
     return doc
 
 
-def addtask(doc, ze_id, title, text, childs):
+def addtask(doc, ze_id, title, text, children):
+    """Initialize GTG tasks in order to display them at first run."""
     t_xml = doc.createElement("task")
     t_xml.setAttribute("id", ze_id)
     t_xml.setAttribute("status", "Active")
@@ -166,7 +350,7 @@
     t_xml.setAttribute("tags", ",".join(tags))
 
     cleanxml.addTextNode(doc, t_xml, "title", title)
-    for c in childs:
-        cleanxml.addTextNode(doc, t_xml, "subtask", c)
+    for child in children:
+        cleanxml.addTextNode(doc, t_xml, "subtask", child)
     cleanxml.addTextNode(doc, t_xml, "content", text)
     return t_xml

=== modified file 'GTG/core/search.py'
--- GTG/core/search.py	2012-05-23 08:55:31 +0000
+++ GTG/core/search.py	2012-07-22 18:10:24 +0000
@@ -54,7 +54,7 @@
 Examples of queries:
 '!tomorrow !or !today' => show tasks which are today or tomorrow
 '@gtg @writing' => show tasks with both of the tags @gtg, @writing
-'@gtg !before 2012-03-01' => show GTG tasks with due_date before Marz 1
+'@gtg !before 2012-03-01' => show GTG tasks with due_date before March 1
 'buy @errands' => show errands where I have to buy something
 '!not buy @errands' => show errands without keyword buy
 '!after "next month"' => show tasks after this month

=== added file 'doc/userdoc/C/gtg-search-intro.page'
--- doc/userdoc/C/gtg-search-intro.page	1970-01-01 00:00:00 +0000
+++ doc/userdoc/C/gtg-search-intro.page	2012-07-22 18:10:24 +0000
@@ -0,0 +1,38 @@
+<page xmlns="http://projectmallard.org/1.0/"
+      type="guide" style="task 2column"
+      id="gtg-search-intro">
+
+  <info>
+    <link type="guide" xref="index#gtg-search" group="first"/>
+    <revision pkgversion="0.1" version="0.1" date="2012-07-03" status="candidate" />
+    <credit type="author">
+      <name>Bertrand Rousseau</name>
+      <email>[e-mail]</email>
+    </credit>
+  </info>
+
+  <title>Use GTG Search</title>
+
+<p>To help you to find specific tasks more easily, GTG allows you to search
+for tasks based on their content.</p>
+
+<p>Searching for tasks is really easy: just type the words you are looking for 
+in the Quick Add Entry, and select &quot;Search&quot; in the menu that
+will appear automatically.</p>
+
+<p>GTG stores your searches in the sidebar, under the &quot;Search&quot;
+section. You can thus always go back to a previous search later on if you
+need it. Search results are updated automatically, so you always get
+all the tasks matching your search request.</p>
+
+<p>GTG also saves all the search requests you have made until you explicitely
+delete them (which you can do by right-clicking on them and selecting
+&quot;Delete&quot;). That allows you to safely quit GTG without loosing your
+search requests. This can be very useful when you use the search features
+to identify specific tasks regularly!</p>
+
+<p>If you want to perform really specific searches, you can use a special
+syntax to create precise requests. Those aspects are covered
+<link xref="gtg-search-syntax">in this page</link>. </p>
+
+</page>

=== added file 'doc/userdoc/C/gtg-search-syntax.page'
--- doc/userdoc/C/gtg-search-syntax.page	1970-01-01 00:00:00 +0000
+++ doc/userdoc/C/gtg-search-syntax.page	2012-07-22 18:10:24 +0000
@@ -0,0 +1,123 @@
+<page xmlns="http://projectmallard.org/1.0/"
+      xmlns:ui="http://projectmallard.org/experimental/ui/"
+      type="guide" style="tip"
+      id="gtg-search-syntax">
+
+  <info>
+    <link type="guide" xref="index#gtg-search" group="first"/>
+    <revision pkgversion="0.1" version="0.1" date="2012-07-03" status="candidate" />
+    <credit type="author">
+      <name>Bertrand Rousseau</name>
+      <email>[e-mail]</email>
+    </credit>
+  </info>
+
+  <title>GTG Search Syntax</title>
+
+<p>When typing your search request in the Quick Add Entry, you can also use
+special keywords to refine your request. The table below describes those keywords.</p>
+
+<table rules="rows" frame="top bottom" ui:expanded="yes">
+<title>GTG Search Keywords</title>
+  <thead>
+    <tr>
+      <td><p><em style="strong">Search Keyword</em></p></td>
+      <td><p><em style="strong">Effect</em></p></td>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td><p><code>word</code></p></td>
+      <td><p>Search tasks which contains this word</p></td>
+    </tr>
+    <tr>
+      <td><p><code>"text"</code></p></td>
+      <td><p>Basically the same as above but allows the space and special characters inside. Literal must be inside "quotes".
+</p></td>
+    </tr>
+    <tr>
+      <td><p><code>@tag</code></p></td>
+      <td><p>Search tasks with this tag</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!after [date]</code></p></td>
+      <td>
+        <p>Search tasks which could be done after this date</p>
+        <p>Look below for the formatting of the <code>[date]</code> element.</p>
+      </td>
+    </tr>
+    <tr>
+      <td><p><code>!before [date]</code></p></td>
+      <td>
+        <p>Search tasks which must be done before this date</p>
+        <p>Look below for the formatting of the <code>[date]</code> element.</p>
+      </td>
+    </tr>
+    <tr>
+      <td><p><code>!today</code></p></td>
+      <td><p>Search tasks with a due date happening today</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!tomorrow</code></p></td>
+      <td><p>Search tasks with due date happening tomorrow</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!nodate</code></p></td>
+      <td><p>Search tasks without due date</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!now</code></p></td>
+      <td><p>Search tasks with due date defined as "now"</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!soon</code></p></td>
+      <td><p>Seach tasks with due date defined as "soon"</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!notag</code></p></td>
+      <td><p>Search tasks without tags</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!someday</code></p></td>
+      <td><p>Search tasks with due date defined as "someday"</p></td>
+    </tr>
+    <tr>
+      <td><p><code>!not [query]</code></p></td>
+      <td><p>The next part of the query will be negated</p></td>
+    </tr>
+    <tr>
+      <td><p><code>[query] !or [query]</code></p></td>
+      <td><p>Return True if at least on of elements is true</p></td>
+    </tr>
+  </tbody>
+</table>
+
+<p><code>[date]</code> can be formatted as yyyy-mm-dd (for example 2012-04-01)
+or yyyymmdd (20120401) or mmdd (0401 - the year being implicitly the current
+one) or today, tomorrow or a weekday name (due:monday means due next Monday).
+</p>
+
+<p>All elements of the query must be true for the query to be true. In other words,
+the search feature behave like it add an implicit logical 'AND' between each element.</p>
+
+<p>Examples of queries:</p>
+
+<p><em style="strong"><code>!tomorrow !or !today</code></em></p>
+<p>Show tasks which are today or tomorrow</p>
+
+<p><em style="strong"><code>@gtg @writing</code></em></p>
+<p>Show tasks with both of the tags @gtg, @writing</p>
+
+<p><em style="strong"><code>@gtg !before 2012-03-01</code></em></p>
+<p>Show GTG tasks with due_date before March 1</p>
+
+<p><em style="strong"><code>buy @errands</code></em></p>
+<p>Show errands where I have to buy something</p>
+
+<p><em style="strong"><code>!not buy @errands</code></em></p>
+<p>Show errands without keyword buy</p>
+
+<p><em style="strong"><code>!after "next month"</code></em></p>
+<p>Show tasks after this month</p>
+
+</page>

=== modified file 'doc/userdoc/C/index.page'
--- doc/userdoc/C/index.page	2012-07-09 15:18:39 +0000
+++ doc/userdoc/C/index.page	2012-07-22 18:10:24 +0000
@@ -43,6 +43,10 @@
     <title>Task Management</title>
  </section>
 
+ <section id="gtg-search" style="2column">
+    <title>Search For Tasks</title>
+ </section>
+
  <section id="gtg-sync" style="2column">
     <title>Sync Services</title>
  </section>