No doubt, whpalmer, you have a point too.
It all comes down to different tastes and priorities, obviously. For me, simplicity is about having clear and unambiguous conceptual categories. For others, simplicity is about visual presentations. For others still, it boils down to minimizing the number of clicks to access your information.
It seems overall that Curt's suggestion (projects and action groups being actionable and automatically placed in their own "bin") makes both camps happy. If no such "bin" is implemented, at least there should be a "default context" setting for projects and groups in the app's preferences. That way we can create our own bin of sorts by having a special "Projects/Groups" context automatically assigned to parents.
It all comes down to different tastes and priorities, obviously. For me, simplicity is about having clear and unambiguous conceptual categories. For others, simplicity is about visual presentations. For others still, it boils down to minimizing the number of clicks to access your information.
It seems overall that Curt's suggestion (projects and action groups being actionable and automatically placed in their own "bin") makes both camps happy. If no such "bin" is implemented, at least there should be a "default context" setting for projects and groups in the app's preferences. That way we can create our own bin of sorts by having a special "Projects/Groups" context automatically assigned to parents.
Threaded Mode