Excellent resource! I'm particularly excited to get started using dependencies. I have way too many projects whose dates always change (clients change priorities). My "To Do" view gets full of stuff I haven't done, and I find myself creating elaborate prioritization schemes which seem like good ideas at firts, but invariably end up making things worse. The simplicity of the dependencies (and having the next items pop up in the list only when they're workable) sounds like it could be a lifesaver!
I'm particularly interested in something I read towards the end of the ECCO EXT Doc:
"I will soon create a rule to mark the goal done as soon as all the sub-tasks are done... Since I organize my actions by the context in which I can perform the action, the dependencies will remove the goal from view if thenext actionable task associated with that goal needs to be performed in another context. Pretty slick!"
Yes, it does sound pretty slick. It also sounds like about the only way I can think of to have multiple predecessors that feed a single successor (the multiple predecessors would have to be subordinate to a higher level item which ITSELF is the item that triggers the successor when it's "done"). So I'm wondering if you've done anything with that yet
Thanks for all your hard work!!
Scott <><