Quote:
|
Originally Posted by michelle
Ok . . . I didn't give a great example. I should have put calls at the top of the hierarchy (Calls>Office>Fred). But it shouldn't matter because contexts will be completely customizable to fit your workflow. I just wanted to throw the idea of hierarchies out there. We are considering doing tags as well, but I'm not sure it will make it into 1.0.
|
I assume that you mean we can have nested contexts, and be able to "focus" on Calls and see everything in every sub-context below it. If I understand correctly, this would be great; I'm trying to use iGTD, and this is a huge stumbling block for me.
I can see some use for tags as well. Even though OmniFocus is aimed at being a GTD application, some people might find tagging more useful than hierarcial contexts. (And in the end, it's about being productive, not slavishly adhering to a single methodology, right?)