BoofleBlog

Why hasn’t anyone done this for Windows? Wouldn’t it be cool if they shared the same API? So that there would be a “universal” sort of call for application developers to build?

Sounds like a project!

Comments(0)

I’ve been trying to make some very basic design decisions about The Elephant. My first thought was a hierarchical organization — Categories have Projects and Projects have Actions. I was going to be flexible — a project could exist without being part of a category and an action could exist without a project. As I think more on it, I become more convinced that hierarchies are bad. Tags are the hip new thing. With tags, I don’t have to worry about who’s a part of what — I can just go with the flow.

But wait — I’m not a flower. I’m too rigid for tags. Maybe a tree is the right setup for me. One thing I want The Elephant to do for me is to figure out if any Projects don’t have Actions. (GTD teaches us that we can’t “do” a project — we can only do actions so we need to figure out the Next Action for any project in order to move ahead.) Tags won’t show me what projects are unActioned. So maybe a tree is the way to go.

I think it’s time to sit down and write use cases for this bad boy so I can figure out what he needs to do.

Comments(0)

This is going to be my nice, straightforward to-do manager. It’s called the Elephant for two reasons:

1. “Elephants never forget.” I doubt that’s true, but enough people think it’s true that it doesn’t matter. In any case, the plan is for this Elephant to keep me from forgetting.
2. “Eating the elephant” — there’s an old story or joke that floats around the back of my mind — I can’t remember any details, but I remember that the only way to eat an elephant is piece by piece. This list should help me break up the pieces of the elephant into managable chunks.

This is also going to be my first PHP project — I’m looking forward to it.

Comments(2)