Expanding on the basic idea of virtual-tiddler nodes, and along similar lines to fieldname nodes and tagname nodes:
I’ve updated the quick-demo site to include templated handling of color-value nodes. I’ve chosen to apply this hex-color-value template via a cascade condition specific to “missing” tiddlers that start with # and fit the 3- 6- or 8-digit hexadecimal pattern. In principle, it can be extended to cover named colors, rgba, hsv, etc.
So, for a node such as #9ac5df you would see a swatch of the color (with gradient background to help illustrate transparency, if present), plus:
- Summary of where this color appears in the current palette (e.g.
button-background) - Summary of which tiddlers have this value in
colorfield (e.g.$:/springer/MoreSideBar/EmptyTags).
This step continues proof-of-concept for virtual-tiddler-nodes. So far we have 4 intuitive KINDS of semantically straightforward virtual nodes (which may overlap):
- tagnames
- fieldnames [potentially clothed with a special prefix]
- filter expressions
- field/index values (for
color, formodifiedetc.) [potentially clothed with a special prefix]
As discussed with @TW_Tones, it is possible to approach these “intuitive” nodes in (at least) THREE ways:
- using
$tags/ViewTemplate(with conditional framing) — ideal if you’d want the same content even after a tiddler is created at that node - following a condition in main cascade for body template (with or without specifying that the tiddler
!has[title]) - through a narrower approach specific to “missing”-tiddler nodes — as a complication of (or replacement for)
$:/language/MissingTiddler/Hint— potentially a cascade rooted there.
Each of these 3 approaches has pros and cons!
(Note, in addition to what I’m calling “intuitive” virtual-tiddler nodes, there’s at least one other way in which “virtual nodes” might be developed for more technical purposes, as described in this thread.)