Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-12-17 07:40:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Tips and tricks (markdown)

Popsch 2012-02-18 20:36:09 -08:00
parent 0be12961ce
commit b4101c89bb
1 changed files with 36 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

60
Tips-and-tricks.md

@ -1,47 +1,59 @@
## Getting an Inbox
Many other software packages support an inbox. You can achieve the same in TRACKS by defining a project called _@Inbox_ and a context called _@nocontext_. You can set this context to be the default context in the preferences. Now, if you don't immediately want to define a project, just specify the project to be _@Inbox_ and the context to be _nocontext_. You can then later review the inbox and go through the created tasks. This page contains a collection of tips and tricks to speed up your work with Tracks and to structure your work with Tracks.
## Learn the access keys # Speeding things up
### Learn the access keys
Many views have access keys. This speeds up navigating and saves time. Many views have access keys. This speeds up navigating and saves time.
## Hide completed actions in the overview ### Use the template scripts in the /doc directory
To hide completed actions just go to the preferences and set the number of shown completed actions to zero.
## Use the template scripts in the /doc directory
You often have recurring projects which follow specific structure (e.g., travel, filing taxes). *Note* that these are not recurring actions. For recurring projects there is a template script in /doc which permits easily instantiating You often have recurring projects which follow specific structure (e.g., travel, filing taxes). *Note* that these are not recurring actions. For recurring projects there is a template script in /doc which permits easily instantiating
## Hide projects you can't work on in the near future ### Use the action drag&drop to quickly define dependencies
You often will have projects that you cannot work on or that depend on some external event to happen. Just hide them, so they don't clutter the home screen. Each action has a little grab-able bar between the description and the quick menu. The mouse pointer forms a hand over it. Use this to drag&drop the action onto other actions to define a dependency.
## Use only lower-case for everything ### Keyboard-driven project selection
You will often type things quickly and then the autocomplete will be unable to keep up with you. This can cause you to accidentally create new projects like one for _misc_ although you wanted it in the project _Misc_.
## Application-like feeling in Google Chrome
To get an application-like feeling with tracks, start it in Google Chrome with --app= like
google-chrome --app=http://localhost:3000
## Keyboard-driven project selection
In Google Chrome, you can quickly access a project through the following key combo. Depending on your operating system, your access keys might start differently than _Alt_, but I'm sure you get the idea. In Google Chrome, you can quickly access a project through the following key combo. Depending on your operating system, your access keys might start differently than _Alt_, but I'm sure you get the idea.
Alt-P Ctrl-F <search string> Esc Return Alt-P Ctrl-F <search string> Esc Return
## Retrieve your task list through a Jabber-compatible client ### Retrieve your task list through a Jabber-compatible client
Add tracks.bot@gmail.com as a contact and use the gtd command to set your feed URL. Once its set up, you can retrieve your task list by simply typing gtd without a URL. Add tracks.bot@gmail.com as a contact and use the gtd command to set your feed URL. Once its set up, you can retrieve your task list by simply typing gtd without a URL.
## Things to do with tags # Structuring things
### Getting an Inbox
Many other software packages support an inbox. You can achieve the same in TRACKS by defining a project called _@Inbox_ and a context called _@nocontext_. You can set this context to be the default context in the preferences. Now, if you don't immediately want to define a project, just specify the project to be _@Inbox_ and the context to be _nocontext_. You can then later review the inbox and go through the created tasks.
### Hide completed actions in the overview
To hide completed actions just go to the preferences and set the number of shown completed actions to zero.
### Hide projects you can't work on in the near future
You often will have projects that you cannot work on or that depend on some external event to happen. Just hide them, so they don't clutter the home screen.
### Use only lower-case for everything
You will often type things quickly and then the autocomplete will be unable to keep up with you. This can cause you to accidentally create new projects like one for _misc_ although you wanted it in the project _Misc_.
### Application-like feeling in Google Chrome
To get an application-like feeling with tracks, start it in Google Chrome with --app= like
google-chrome --app=http://localhost:3000
### Things to do with tags
Tracks users apply tags in the following ways: (add your own) Tracks users apply tags in the following ways: (add your own)
* Add people's names to tasks so when you see them you can easily see what tasks depend on them by clicking on the tag. This is a mix of a context and a quick search thingy. * Add people's names to tasks so when you see them you can easily see what tasks depend on them by clicking on the tag. This is a mix of a context and a quick search thingy.
* Add approximate activity durations as tags. Short for less than 5min, medium for 20-30min block, and long for a 1 hour undisturbed bock. * Add approximate activity durations as tags:
* Short for less than 5min, medium for 20-30min block, and long for a 1 hour undisturbed bock.
* 10 for 10min, 20 for 20min, 30 for 30min, ...