I agree but through this card mechanism we can add behaviours such as delist, special ordering logic and more without disrupting imported solutions that don’t know about this.
- I still maintain the value of the $:/tags/ViewTemplate
Agreed hence this card approach, and the possibility of adding advanced relationally-complex supportive features
That can be true, but now we can add tools to support the maintenance because with a cards solution we need not be so tightly bound to legacy methods.
Approach
Introduce mechanisms that support the ability for tiddlers to have many simultaneous roles.
other notes
My prior reply above to find solutions in this multi-role approach is a design exploration and we need not concern ourself whether this would be added to the view template, view cascade or independent cards model.
Even this Topic is all about how do we make inroads to complex solutions.
@Springer have a look at @pmario’s solution WikiLabs DevTools Plugin — Browser-Side Developer Tools for TiddlyWiki which may be a way of accessing insight to cascades and cards by overlaying a tool you can remove later, rather adding additional weight into wikis.