Mark, I have two responses, and then I really have to get things done! :-)
1. My point about history was to emphasize the origins of what is a version 1.x product. OmniFocus has already evolved beyond Kinkless's UI, but short of a radical redesign, it's going to retain some of those UI features, especially in 1.x. Maybe 2.0 will feature a radical interface redesign. But I hope not, because:
2. I think there is a good reason for retaining the distinction: it's the distinction between commitments/outcomes/goals that can't be done in one concrete step (projects) and steps toward them (actions). In another thread you remarked that project and context views are just different ways of looking at actions. I disagree; I consider the action to be a means to accomplishing the project, and the context as a means (in a broad sense) to accomplishing the action. I find that the distinction between planning mode and context mode brings me a real benefit because it corresponds to how I conceptualize planning and doing.
And now, back to work!
1. My point about history was to emphasize the origins of what is a version 1.x product. OmniFocus has already evolved beyond Kinkless's UI, but short of a radical redesign, it's going to retain some of those UI features, especially in 1.x. Maybe 2.0 will feature a radical interface redesign. But I hope not, because:
2. I think there is a good reason for retaining the distinction: it's the distinction between commitments/outcomes/goals that can't be done in one concrete step (projects) and steps toward them (actions). In another thread you remarked that project and context views are just different ways of looking at actions. I disagree; I consider the action to be a means to accomplishing the project, and the context as a means (in a broad sense) to accomplishing the action. I find that the distinction between planning mode and context mode brings me a real benefit because it corresponds to how I conceptualize planning and doing.
And now, back to work!
Threaded Mode