Quote:
Originally Posted by MacDork
I have another example that might be a better example of why I'd like to be able to set more than one context to an action.
EXAMPLE 1
---------------
Let's say I have an action "Buy OmniFocus" and it's context is @online.
I have access to the internet from home and at work. I COULD create an @online context independent of my @Work and @Home contexts, but the need for discrete versions of @online can also be made, thusly:
-- "Catch up with facebook friends" @work/online is a no-no.
-- "Read super secret work document" @home/online won't work because I don't have vpn
In the case of "Buy OmniFocus", it's appropriate and suitable to set it's context to either/both "@work/online" or "@home/online". If I could set it to both, I'd be reminded to buy it when I was both at home and at work.
|
Instead of having @work/online and @home/online, have @online, @online/home, and @online/work. Stuff you can do either at home or work goes in @online, stuff that has to be done at one or the other goes in the proper subcontext.