This is a follow-on from an earlier post about getting organised using Ruby scripts. The first step is to get some kind of system in place to managing the things I need to remember - a Todo list tool.
First off, I'm not going to build if something already exists. I think that it's great that we as a community - and I'm thinking of the larger programming community - try to solve the same problems in different ways. It may look inefficient from an external point of view, but it's really actually the most optimal way of solving problems - follow as many paths as possible to find the best reusable one.
But that's the topic for another post.
A quick google reveals numerous Todo list applications written in Ruby. The topic seems a perennial favourite in Ruby coding competitions. Chances are looking good I'll find a suitable starting point for Argh!
But before I start looking, some constraints. What do I want from a tool?
MUST be simple to use
SHOULD work across different computers
The last two come from the folks at Reddit. Makes sense.
As for time contraints, I can't spend more than about 30 mins having a look - it's the weekend and there's stuff to do with the family. Here's the top hits:
A small, simple Todo manager. Exists as a Gist, but with a couple of forks that might be worth following. Has a basic tagging system using '@' identifiers.
Can create, delete, list etc as expected. Can change priority using 'bump' command. Defers filtering on '@' identifiers to the system's grep.
# Add todo items $ todo add Check out rubyrags.com Add: (1) Check out rubyrags.com # Create a todo with context $ todo add Buy Duck Typing shirt from rubyrags.com @work Add: (2) Buy Duck Typing shirt from rubyrags.com @work $ todo add Buy Ruby Nerd shirt from rubyrags.com Add: (3) Buy Ruby Nerd shirt from rubyrags.com # List todo items $ todo list 1. Check out rubyrags.com 2: Buy Ruby Nerd shirt from rubyrags.com @work 3: Buy Duck Typing shirt from rubyrags.com @work $ todo list @work 1: Buy Ruby Nerd shirt from rubyrags.com @work 2: Buy Duck Typing shirt from rubyrags.com @work
Interesting approach - essentially one project per directory. Has a Twitter-like tagging model; people (@joan, @peter), contexts (#important, #home) and item sets (%fix_computer, %do_many_small_tasks).
I tried installing Dooby under Ruby 1.9.3 and had a few issues. Not sure what's going on but didn't have the time to get bogged down in debugging. The exercise is to see what's on offer, kick the tyres later.
# Add todo items, using @people, #context and %item_sets tags $ dooby add "#fix the email error in %website, check this out with @peter #today" $ dooby a "learn to use the #aliases of the #commands " $ dooby a "#pair with @jim on the %tickets module" # List todo items $ dooby list @peter $ dooby l today $ dooby l "#today" $ dooby l %website
I wanted to review at least three, but the more I looked the more sketchy the Todo apps looked. I also chewed up my allotted time too quickly. Still easily distracted.
I did look at the todo gem, but it doesn't look like it's been touched in a while.
There was also another command line app Tudu that sprung up in searches. But once I started leaning out of Ruby-space it really was time to stop.
As noted before, Todo apps appear in Ruby comps fairly regularly. I might need to look further into the results of the CodeBrawl comp - NB Matt Sears' entry came in second in that comp.
If anyone knows any code I should have a good look at let me know!
Right now, I want to start with something simple. Matt Sears' gist looks pretty decent for a one pager (not including the tests). Dooby looks like fun but, as commented on by Bill Dueber in the previous post, the whole point of this exercise is to get things together and happening. I've love to have Dooby's multiple tags model in Matt's code though.
Neither of the two solutions I've looked at can work across computers, nor have a mobile interface. The winner of the CodeBrawl comp seems to use Github Gists as the repo model. Interesting, but not sure I'd want all my data public. Anyway, the next step is to actually get something installed, and we can book-strap from there. Onwards, forwards.
Future post: Argh! Coding Begins