Pierre, et al
Thinking of automation as exists w Zoot smart folders, I'm considering the following scenario:
Populate the 'Inbox' w a lot of check mark category columns. Example
| house | car | ToDo | Finances | girlfriend | tech | journal |
Then create views for / house / car / todo / finances / girlfriend / tech / journal/ with Inbox as source
Specialized views are then created & this method would automatically populate those views w the appropriate data
First, I'd like comments on this approach.
Second, what's a better approach for this kind of thing?
Third, the problem I see comes in the specialized views. Example: Tech
Let's say I use 10 different programs & I want to amass all tech notes in this view
What's the best way to filter for the individual program notes.
I could re-create the cascading views as I've done above but that seems kludgy to me
Thanks.
Comments
Auto-Assign Rules
Auto-Assign Rules are used to assign values to other fields when values in this field is changed. They are also called Push-Equations (as opposed to Pull-Equations discussed here). The syntax is Flags:Field = equation/value.
The flags indicate when the rule should be applied (they can be combined):
- A: flag: Action will be triggered when a value is added (initially no value in the field)
- M: flag: Action will be triggered when a value is modified (initially there is a value in the field)
- E: flag: Action will be triggered when a value is deleted You can have as many auto-assign rules as you wish separated by vertical bars, they'll be executed in the sequence that they are entered.
Here is an example that calculates the color when a field is added or edited and clears the ItemColor when the field is erased: AM: ItemColor=CalcColor (DurationHr - BudgetHrs) | E: ItemColor=Push equations are actually more efficient than Pull equations, since it is the field that is causing a change that triggers the calculation to run. Plus they allow many equations in a single field.