Quote:
...As an example, ... It would be nice to be able to pull all of those together at the same time and complete them most efficiently.
|
--
JJW
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!
|
Member
2011-10-04, 05:56 PM
Quote:
-- JJW
Post 11
|
Member
2011-10-05, 07:52 AM
Quote:
I may have mislead some folks by choosing a poor example, but the larger point is this: If you can only assign one context, then *by definition* you cannot efficiently set up contexts that run across two or more dimensions. In other words, you can have either "location-based" contexts, or "people-based" contexts, or "energy-based" contexts, or "time-based" contexts, or "equipment-based" contexts -- but you have to choose one, because you cannot have all of them (or, to be more precise, you *can* have them all, but if you do, then you are forced to scan multiple context lists).
Post 12
|
Member
2011-10-05, 08:04 AM
Quote:
All I want is to be able to pull up a list of tasks that I can complete at "home" and have that list contain every task that I can complete at home. I don't want to have to check multiple context lists -- I just want to see my list of things I can do at home. But there are only two ways to accomplish that: 1. One way to accomplish it -- what I do now, in fact -- is to assign every task that I can do at home to "home." Works ok, but the downside is that I can't use contexts like "low energy" or whatever, because some of those tasks could also be completed at home (and some not), and so if I give them one of those alternative contexts, then they no longer show up on my "home" list. (And creating a perspective that shows the union of "home" and "low energy" does not solve the problem, because some "low energy" tasks are NOT home tasks, so the union list is overinclusive.) 2. The other way to accomplish it -- which OF does not currently support -- is to simply allow multiple tags. That way, I can tag all of those items with the "home" tag AND also give them whatever other tags I think might be useful for me. The point is not that I would search for items containing both tags at once (overkill), but rather that searching for either tag by itself would give me a complete list. Last edited by Stargazer; 2011-10-05 at 08:08 AM..
Post 13
|
Member
2011-10-05, 08:16 AM
Quote:
Post 14
|
Member
2011-10-05, 08:58 AM
Quote:
Put another way ... in my specific set of contexts, location trumps all others when location is an absolute specifier for the action. In your example, I cannot change the air filter anywhere but @home, regardless of how much energy and time I might have. Of course, no one chains me to my desk at work, and I _could_ in principle get up now, drive home, change the air filter, and drive back to work. That is however rather silly. So, for me, this task is by no means Low Energy compared to @Home. After that, my "Waiting For" context follows. Any task that is someone elses to do is a "Waiting For". Again, try as hard as I might, I cannot collect the budget numbers from last years program review when those numbers are only accessible by the accounting department. Anything not fitting the above is at my discretion to set in context. That is where I use the outcome/energy contexts. I can call the contractor at my father's house anywhere and anytime I choose. So, the context for that action is based on where that action fits as an outcome/energy decision in my project "Renovate Father's House". In an inverse consideration, I wonder if, while sitting at your office without the boss around, you pull up your Low Energy context and are fully pleased to see the "Change Air Filter" task appear on your list of possible actions. -- JJW
Post 15
|
Member
2011-10-05, 09:14 AM
Quote:
I find that Approach B works far better for me. You seem to have a stronger preference toward Approach A. Nothing wrong with that (though Approach A does seem to me to involve a bit more energy in thinking at both ends -- inception and event). What you are finding now is, OF is limited in allowing you to do type A approaches. At this point then, perhaps a feature request to OG would be in order. I have put in one for tags -- not because I want to do Approach A, rather because when I file away my completed actions for my activities reports or project wrap-ups, I would have a significant benefit in being able to filter projects, groups, and actions by tags. -- JJW
Post 16
|
Member
2011-10-05, 12:56 PM
Quote:
Tagging was my main reason for giving up on Things, it makes me overanalysing. Through tips around this forum and some excellent scripts I have managed to work around the very few drawbacks I can think of lacking multiple contexts/tags. Having worked a bit with databases myself I can share one thing I learnt: Tags belong in free form databases, they will never work well in a structured matrix like that of OF. Although you indicate your needs for tags are linked to your personal preferences rather than professional needs, I think you should really consider one of the three following, either as a replacement or in addition to OF: a) a proper project management tool b) a relational database tool with advanced filtering possibilities or c) A free form database tool. Trying to force OF or any other GTD-software into the world of advanced project management or analytical task approach will corrupt the underlying concept, in my view. What you ask for above is a huge task for any developer and requires answers to a lot of questions like the obvious first three: - How would you suggest it should look when you see your "low energy"-list in terms of columns? - How would you sort tasks to identify only those that meet the combination of @home AND "low energy" in this view you envisage; would there not be (possibly) hundreds of task NOT meeting exactly the two criteria you give? - What is your answer to the technological-philosophical issue: Is a context and a tag really the same thing? (They are often distinguished as a context being pragmatic/fixed and a tag being analytical/relative. Cf. the distinction of structured data and free form databases) To me, it sounds difficult to achieve multiple contexts without the introduction of advanced filtering and analytical procedure - again, back to complex ad hoc queries à la Things OR towards a relational database setup that allows for preset advanced filters. Personally, I wish for neither. In my view, your only chance would be to provide Omni's developers with sketches and elaborated illustrations of your ideas and needs - and I am certain they would read through it. Good luck whatever you choose!
Post 17
|
Member
2011-10-05, 05:53 PM
Quote:
My feeling is that it would tend to cause me to fail to do the task rather than do it more efficiently. This would be a task that takes about 5 minutes out of a project that will last between 2 weeks and 3 months. I think what would end up happening is that I would be checking a context with no next actions frequently just to be sure that I didn't miss any screenings. I would suspect that the most time I end up spending on this particular task for all projects is about 20 minutes a month. There is a lot of wasted time consisting of opening my favorites menu, selecting the correct link, typing a password and user name then doing the search. So being able to call a tag to see if I can run any more searches now that I have the tool loaded would significantly makenlife easier
Post 18
|
Member
2011-10-06, 07:49 AM
Quote:
But it doesn't actually resolve the issue that you can really on set contexts efficiently along a single dimension, because the subcategories by definition cannot apply across different contexts. They let you slice the loaf into thinner slices, but you can't cut in a different direction, if you see what I mean. Quote:
Post 19
|
Member
2011-10-06, 08:19 AM
Quote:
Such tasks would be marked in context ☼Screening. During a review of a Project, I would see a Next Action -- ☼Screening (is DUE). I would start that, and correspondingly call up the ☼Screening context list to see if any other such tasks are pending (/ DUE). I would handle them appropriately. I would subsequently ONLY go back to ☼Screening context when a review at a project level showed, my next action is a task that is again in that context. Otherwise, I would leave well enough alone and get about doing the other tasks on the project(s). In other words, ☼Screening would not be a temptation call for frequent visits to see if "I need to go there now". Rather, it would be the notice that, when I am otherwise and/or required to be specifically active in that context (doing my screening), there is a list of other such tasks that might be done at the same time. I think of the context as a frame of mind or state of current action rather than a call to required actions. Hope this gives room for thought if nothing else. Thanks. -- JJW
Post 20
|
Thread Tools | Search this Thread |
Display Modes | |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can you have too many contexts? | marker | OmniFocus for iPad | 7 | 2011-02-28 10:08 AM |
How many contexts are TOO many contexts? | filmgeek | OmniFocus 1 for Mac | 10 | 2009-08-06 01:08 AM |
Showing contexts in "All Contexts" | tswartz | OmniFocus 1 for Mac | 20 | 2008-09-08 08:17 AM |
Contexts | sco2th | OmniFocus 1 for Mac | 2 | 2008-01-25 02:42 AM |
Contexts | samaparicio | OmniFocus 1 for Mac | 5 | 2006-11-14 06:00 PM |