Those two views are worse than unnecessary; they're between OmniFocus and SHIPPING!
Defer those non-canonical boondoggles to 2.0.
Defer those non-canonical boondoggles to 2.0.
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!
|
|
FAQ | Members List | Calendar | Today's Posts | Search |
Single Actions ? | Thread Tools | Search this Thread | Display Modes |
Those two views are worse than unnecessary; they're between OmniFocus and SHIPPING!
Defer those non-canonical boondoggles to 2.0.
Post 51
|
Quote:
Post 52
|
Guest
2007-08-04, 01:38 PM
Quote:
Almost a month later and I haven't heard word of its inclusion. Can someone from omni tell me if this is still planned? And if so, any idea when?
Post 53
|
I feel as if, in recent builds, the concept of the singleton/single action/atomic task is getting relegated to second-tier status in favor of projects.
It used to be that I could go to context view, pick a context, and add a whole host of next actions by hitting Return after each line item -- which is useful if I'm processing my physical inbox or other collection bucket, or creating a quick shopping list in one of my contexts. Then actions with a context and no project became inactive actions, which can only be seen if you're viewing remaining or all actions. Somewhere around the same time, hitting Return to create a new line item in a context broke, and hasn't been fixed as of build 90172. Then this idea of a "singleton project" appeared. I'm hoping this is a placeholder for a real single-action view because I am now required to either assign a Next Action to my singleton project when I create it using Quick Entry, or I have to: Create an entry Send it to the Inbox Use Clean Up to move it to the context list (and default "singleton project") This, coupled with the broken ability to create new items directly into a context list, have needlessly complicated the elegant workflow that was present when I first started using OmniFocus. As I said, I hope the "singleton project" goes away and is replaced by a view similar to the Inbox, and single Next Actions do not have to be intentionally assigned to anything other than the context they inhabit. I still find Omnifocus an incredibly useful program. I just think the current incarnation is much less easier to use than it was in the beginning.
Post 54
|
Member
2007-08-19, 05:01 PM
Post 55
|
Now, I hope the "singleton project" concept stays, it's a nice, useful concept,that I have high hopes of being able to implement a digital Tickler file with.
But I absolutely, positively refuse to lump all of my single actions together in one bucket project just because they are alone. It's an awful idea having to set up the proper implementation of single actions when they used to work PERFECTLY before they were fiddled with. Now you can't even remove a task from your inbox unless it has a project, which is so bassackwards I can barely function in OF anymore.
Post 56
|
Member
2007-08-20, 12:58 PM
GeekLady, when you say they worked perfectly, was that when actions without projects showed up in context lists?
I liked that "no project, context assigned"=="do-able item". But it wasn't perfect, because I rely heavily on the folder focus, and focusing on a folder meant no single actions showed up. So I had to use the "project for singletons" idea anyway. I disliked that very much, especially that the first one was a next action. This is a *slight* improvement. I really want to leave the project blank, but tag an action as belonging to a certain folder. That would be my perfect solution. I don't know if that's possible given the "folder" implementation.
Post 57
|
Member
2007-08-20, 01:13 PM
Post 58
|
Member
2007-08-20, 01:37 PM
Quote:
What is the barrier to having these tasks just be individual projects under a folder. Is it that there are too many to scroll through, is it that they don't have the right behavior in Context view? I'd like to hear a discussion about this and why some folks have gravitated towards using singletons.
Post 59
|
Quote:
Single actions could be placed in a project, but sometimes just a list of single actions is quicker and easier to create and complete. But then, maybe I just haven't thought through my projects (or roles) clearly enough.
Post 60
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can I sort actions in a Single Actions folder? | lessing | OmniFocus 1 for Mac | 2 | 2012-11-27 03:44 PM |
Pausing some actions under a single actions list pauses the whole single actions list | zdlo | OmniFocus 1 for Mac | 6 | 2012-08-27 09:08 PM |
Projects vs single actions | abowen500 | Applying OmniFocus | 0 | 2011-10-12 08:03 AM |
Single actions can't be put on hold? | Frosty Crunch | OmniFocus 1 for Mac | 29 | 2007-10-17 04:16 PM |
Single Actions in every folder? | djbell | OmniFocus 1 for Mac | 4 | 2007-09-14 02:55 AM |