Tag Archives: GTD

things2thl – migrate from Things to The Hit List

I’ve been meaning to give The Hit List a good try since I got it as part of the Macheist 3 bundle. However, I have to continue tracking my tasks, and I have all of them already in the awesome Things (about which I have written before). So I have spent the last few days putting together a script to migrate my data from Things to THL. You can find it here: http://zzamboni.github.com/things2thl/. You can install it as a gem package or download the source code. There is not much documentation for now, but look at the help (things2thl -h) and you should figure it out quite easily.

If you find anything that is broken, or you have any type of feedback, please let me know (ideally, create an issue in github).

A full review of THL will follow when I’ve had a few days to play with it.

Links: Weekend Watching: Merlin Mann on Maximizing Your Time

Weekend Watching: Merlin Mann on Maximizing Your Time – Merlin Mann's talk at Google. (tags: productivity gtd lifehacks @readlater )

Links: Time & Attention Presentation: "Who Moved My Brain?" | 43 Folders

Time & Attention Presentation: "Who Moved My Brain?" | 43 Folders – Very useful presentation about managing your time, reducing interruptions, and making better use of your brain. (tags: productivity gtd 43folders presentations )

My GTD system

Here’s my mapping from David Allen’s GTD workflow to the parts in my system that implement each component. My main electronic tools are Things (http://culturedcode.com/things/), Journler (http://journler.com/), Mail.app and iCal. My main physical tools are my HPDA, my physical tickler file, my A-Z filing cabinets and my “inbox” and “pending” boxes.

(the workflow image is © David Allen & Co.)

Posted by email from zzamboni’s posterous

Things gets synchronization abilities

The latest version of the Things task manager (0.9.2) incorporates synchronization and support for Leopard’s system-wide to-do’s! As has become the norm with Things, the new feature is extremely well thought-out, and in my testing so far it works flawlessly.

This was the big feature I was most expecting, since it gives me back the ability to carry some of my to-dos on my cell phone, with the ability to add new ones or check them as done.

My del.icio.us bookmarks for May 24th

Ready-Set-Do! – GTD tool/methodology for Mac (tags: @readlater gtd productivity )

How to use Things on two accounts on the same machine

I am a big fan of Things, the very nice task manager from Cultured Code. I keep both personal and work-related tasks in it, and in my Mac I have two accounts, for personal and work-related use. This leads to me having to run Things on both accounts, while sharing the same database. Here’s how I do it:

  • In one of the two accounts, I created a symlink from ~/Library/Application Support/Cultured Code into the corresponding directory of the other account (my two accounts are named “dza” and “zamboni”, and I created the symlink in “zamboni”:
    zamboni% cd Library/Application\ Support
    zamboni% ln -s ~dza/Library/Application\ Support/Cultured\ Code .

    This makes Things access the same files regardless of which account uses it.

  • Make sure that both accounts can read and write from that directory. In my case, both my accounts belong to the “staff” group, so I simply give the files group-write permissions (you have to do this from the account where the original files are, or from root):
    dza% chgrp -R staff ~/Library/Application\ Support/Cultured\ Code
    dza% chmod -R g=u ~/Library/Application\ Support/Cultured\ Code
  • You have to make sure Things is only run from one account at a time, to avoid them overwriting each other’s changes. To automatically achieve this, I wrote a small script that kills Things if it’s being run by someone else and then runs it in the current account. Simply killing the process is a bit crude, but Things seem to process the signal properly, I have never lost any data by doing this. Here is the script (I saved it as /usr/local/bin/things_launcher):
    #!/bin/bash
    # If it's running as any user other than me, kill it
    if ps axuwww | grep Things | grep -v "^$USER"; then
    sudo killall Things
    sleep 1
    fi
    # Now run or activate it
    open -a Things

    (note: this will only work if you have set up sudo on your machine to execute commands without asking for your password – I am still figuring out how to use the standard authentication dialog in OSX)

  • Now for the final touch, I used Platypus to create an Application wrapper around my script, so that I can run it using Quicksilver. I named it “Things wrapper”, and you can download it here (or you can create your own using Platypus). I gave it the Things icon, but maybe someone with more artistic talent can come up with a better, more representative icon…
  • That’s it! Just run “Things wrapper” instead of Things, and it will automatically kill other copies of Things, and run it in the local account. If you have it already running, it will simply activate it.

If you find this useful, or if you have any feedback, I would love to hear about it.