OK, first we are focusing on a detail;
The equivalent to a remove I use to remove items from a list is 'generate list' -[subfilter<myexceptionlist>]
Now the Big picture
Some Quick notes;
- The Kin operator is a good way to quickly get a list of all related tiddlers, its so easy you can then add or subtract other sets of related tiddlers.
- I don’t want to tell you “how to suck eggs” as they say but this is the quintessential example of the value of breaking the problem down into parts to get a set of simple steps.
- TiddlyWiki can help because you can write a view template that appears on tiddlers and extracts the relevant information on or available from that tiddler.
- This allows you to work through the logic and obtain working filters
- You can then look at combining them to get your final result.
Finally making use of map reduce etc… is often used because you are trying to make use of intermediate values. If instead you use “nested lists” you get to expose all the intermediate values you want, it is easier to troubleshoot, develop and enhance your logic.
- Once you have a deeper and working example of your logic you can decide if there is value replacing nested lists with more advanced filters.
<$list filter="" variable=one>
<$list filter="[<one>.." variable=two>
<$list filter="[<two>.." variable=three>
In here you can use <<currentTiddler>> <<one>> <<two>> <<three>>
</$list>
</$list>
</$list>
The human brain typically can only manipulate around 7 items, concepts or symbols in working memory at a time (its actually set by a time dimension), the more complex the relationships the less items. By breaking the problem into pieces you are analysing, then once understood you can synthesise.