I was delayed in reviewing your demo, and the truth is despite our previous
conversations, I at first felt lost. I think we can add to you
I think in part the reason I was lost was because it is so elegant and
powerful that in someways, it is hard to believe.
So let me voice its functionality and you can feel free to correct me.
Bimlas's Kindred operator allows you to filter based how tiddlers are
related, This relationship can be determined using the default tags field,
or any other field.
Lets consider the use of a table of contents macro. We choose a root
tiddler, and and the toc macro looks for each tiddler tagged with the root
tiddler, listing its child(ren), it then looks for all the tiddlers tagged
with each child and further down until it can no longer find any more tags
to follow. This produces a TOC for us. You could say that every tiddler in
a TOC is related or a Kindred of the root tiddler. Ie this is a unique set
of tiddlers defined by their membership of this Tree.
Using the filter "[kindred[TableOfContents]]" we will see every member of
this tree, and "[kindred[TableOfContents]count]" will tell you how many
items are in this set (tree).
If instead you target one of the children with the kindred operator you
will have its children and its ancestors returned (not the whole tree)
You can also use kindredup to get the ancestors and this includes with more
than one parent mentioned.
You can also use kindreddown to get the children and grand children etc..
without the parents.
In the case of tags it is possible to have multiple parents, but if you we
using Marios New Here with Parent Button you could use the parent field (as
yet untested by me) you could choose not to have multiple parents. Only
single parents - good for many standard hierarchies. In these circumstances
I believe you will be able to determine the "Path" to an individual tiddler
from the root down.
What is important to understand is you can now rapidly generate lists of
such related tiddlers and use them with additional filters for some very
For example you can find the siblings of Examples with the following filter;
In the above example "Examples" is a child of HelloThere.
I expect we can do some very sophisticated operations with Bimlas's very
helpful Filter Operator. I believe their remains a lot to be explored when
it is simple with filters to do various set manipulations like unions,
removal of one set of items from a larger set of items, not in set etc...
Very good work Bimlas.
Post by bimlas
I just finished my filter operator plugin what I would like to be merged
in to the next release of TiddlyWiki. Before I opening a Pull Request for
it, I want to be sure that this is usefull enough and the behaviour is
clean. Please try out the attached demo and tell me your opinions!
- Find tag intersections in any depth
- Check similiarity between Tiddlers by any field
- Generate Table of Contents dinamically (actually I don't know how to
do, but I'm sure that this is possible)
- Find orphaned tiddlers
- Search in family trees, bus schedules, etc. for common elements
Example: Check similarity between two tiddlers (find common "family
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3db4f196-8dcc-42cb-ba46-01e645eea78c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.