Quote:
Originally Posted by Ken Case
I don't understand how that would work. How would you eliminate the "Grading" group, for example? By replacing it with "Record grades in roster," and making "Grade papers" a child action? But it doesn't really seem to be a logical child, and you could come up with another action that you needed to do after recording the grades (like, oh, securing your notes or something).
|
Ken... please take a look at this website.
http://web.mac.com/stephenzinn/OmniF...on_groups.html
I've detailed Chris's Project in this website using screenshots and manipulated OmniFocus so that it behaves in the following ways:
1. Action Groups can be sequential or parallel.
2. Action Groups appear in the context list.
After creating this example I now believe that allowing action groups to show up in the context list is a critical feature.
My suggestion is to create another grouping in the context list, much like the no context, that shows all action groups with no children.
If the action groups do not appear in some way in the context list,
I believe that people will be fiddling with their OmniFocus software too much, become frustrated with the effort, and stop using OmniFocus.
This is especially true when OmniFocus goes mobile because when mobile a person does not have a full blown version of OmniFocus to fiddle with.
The way that OmniFocus currently works forces a user to constantly be switching back to the projects view to fiddle.
One parameter in your testing of OmniFocus is to see if you can stay in the context view for a day without switching to project view.
Chris... my apologies on the troll comment.
Your attitude has proven me wrong.
Thank you for sharing your outline.