Quote:
Originally Posted by dancingbrook
...when I leave in the morning (without the computer) I hope to accomplish more than just one item from any given project, even if they are sequential. Even if I am in front of the computer, I might logically want to see the next 2, 3 or 4 items in a list...
|
Set your view bar to display "Remaining" or "Available" actions rather than just "Next Actions". It'll then display multiple, upcoming items.
Quote:
Originally Posted by dancingbrook
I could simply have a folder called next actions, or any other set of folders for that matter (like is already there), The point being why either sequential or parallel?
|
It sounds like you want to
manually select actions from a project and actually drag them to a different folder to indicate that they're to be executed next. For better or worse, that's not how OmniFocus is designed (although
Cultured Code's Things sort of works that way).
In OmniFocus, actions stay in your projects, in the order you left them, where they make the most sense. A simple set of rules then automatically determines what's next and available based on action order, the sequential/parallel attribute of their parent container, and sometimes the state of their context (but that's rare).
Using the view bar, you can control how much gets displayed, and in what order, and how it's grouped. At any time, you can go back to a default view and still see all of your actions in their original order, in their original projects.
Quote:
Originally Posted by dancingbrook
Or you could simply just let the next actions be the ones you choose to be next. [snip] I my scenario, I select what's going to appear in my next action lists, including groups if I want.
|
If you're going to manually move items to a "next action list", why not just use OmniOutliner or a text editor to simply drag items from one list to another?
The process of determining what comes next and how actions are related to one another is costly in time and mental effort. It can be distracting if you need to think about it every time you're ready for the next action in a project.
The advantage of OmniFocus is that it allows you to do all that thinking ahead of time and only once. After you've set up a project, the app guides you to what's next so you don't have to go through that process over and over.
Quote:
Originally Posted by Toadling
In fact, it seems like your example shelving project would be impossible to build with what you're proposing.
|
Quote:
Originally Posted by dancingbrook
I have no idea why you reach that conclusion.
|
I think we've simply misunderstood each other. I thought you were suggesting removing the sequential/parallel attribute from containers and adding it to each individual action, and then expecting OmniFocus to still be able to automatically determine which actions should be next or be available. Clearly, that wouldn't work with your example project.
But if you're going to manually choose and move next actions, then I guess you wouldn't need the sequential/parallel attribute at all. Just have one big list, maybe with some organizational folders, and pick whatever you want.
Quote:
Originally Posted by Toadling
I really think Omni Group did their homework here and has thoroughly thought this out.
|
Quote:
Originally Posted by dancingbrook
Good for you
|
Not just for me, but good for
anyone who's interested in using a well-designed GTD app.
My comments are in response to your original assertion that Omni Group somehow failed in their thinking when designing OmniFocus (see
post 8).
But you're last remark feels a little snarky to me, especially when mine was not meant to be offensive. I don't know why you'd be snide about this. After all, I am trying to help you. So perhaps it just got lost in translation.
Quote:
Originally Posted by dancingbrook
I said convergent. You said monolithic. I didn't because I meant what I said. Information from apps is what converges.
|
Actually, you said, "
App convergence and cooperation is the future" (emphasis mine), not "information convergence". Perhaps you meant "data convergence and app cooperation?"
Either way, now that you've made it a little more clear, I think we agree on this point.
Quote:
Originally Posted by dancingbrook
Exactly (re iLife and iWork). LinkBack just provides an active link [snip] That's not the same thing as data syncing as seen in iCal and OF.
|
I'll agree that syncing between iCal and OmniFocus is a big step towards data convergence.
But isn't the "app cooperation" achieved with LinkBack very similar to what happens between the iLife and iWork apps? Having apps that simply work well together, sharing their respective data, even if not the same data, is a step in the right direction. Yet you seem to feel that iLife and iWork are excellent examples, but LinkBack support is not?
Quote:
Originally Posted by dancingbrook
What would you use LinkBack for in OF?
|
Embedding OmniGraffle graphics in OmniFocus projects, maintaining the ability to later edit the graphics in OmniGraffle.
Quote:
Originally Posted by dancingbrook
I'm not sure what you refer to as lots of talk. I've seen nothing, yet it should have been planned from the start.
|
I don't know if it's been planned from the start, or even if it's officially planned at all. But a quick search of these forums reveals several relevant threads. There's even mention of it by an actual Omni Group employee.
http://forums.omnigroup.com/showthread.php?t=7335
http://forums.omnigroup.com/showthread.php?t=6745
http://forums.omnigroup.com/showthread.php?t=7565
http://forums.omnigroup.com/showthread.php?t=2533
Wow, this is one big post. I don't seriously expect you to respond to it. I've already spent too much time on this topic anyway. Good luck and I hope you find something that works for you.