Can anyone explain how the “list-before and list-after mechanism” works?. I understand how to use them, what I am not sure of is how this happens. I am moving the viewTemplate functionality into a custom one and want to know how I may replicate it in a list, rather than a tag.
Thanks for that. It then is clear that list after and before are used to place a tiddler title in an existing list and then are removed. This explains it well thank you.
Now as you said “drag and drop” in the tag tiddler triggers the creation of the list field. It would be nice if an action were available to do this in another trigger.
When using list-before and list-after on tiddlers to be added to the list of $:/tags/ViewTemplate the list- fields do not get removed.
So still a little more to learn but thanks for your insight.
It’s a possibility to add elements to list-fields, without modifying the tag-tiddler, if the tag tiddler is a shadow tiddler. …
As long as you don’t manually use the tag-dropdown to sort the list in the tag tiddler. If you do a manual sort, the shadow-tag will be cloned into a “real” tiddler and the list will be modified.
If the list is manually edited with the tag-dropdown the list-before and list-after fields are removed from the tiddler that contains them. … BUT If you use <<list-links-draggable "shadow-tag">> the list-xx field won’t be removed.
So <<list-links and <<list-links-draggable will show different lists. … That’s a bit confusing …