Mart, I am execited about this too, see and vote for my Idea here <https://github.com/Jermolene/TiddlyWiki5/discussions/5804>
Which reads; *is/all operators to include fields and new system fields! V5.2.0* *Folks,* *Would it be possible to add to the next version is[field] and all[fields]] such that a title can be tested to see if it is a fieldname?* *The following filter can already determine this;[fields[]match[test-field]then[yes]else[no]] equivalent would be [[test-field]is[field]]* *However since fields are a important element of tiddlywiki, it would be helpful and make readable a range of field handling designs.* *An extended feature would be to have virtual tiddlers for such fields like tags currently have a virtual tiddler, you can open and create if desired. This will be even more appealing with the new expanded tiddler naming rules because one could arguably have system fields ie those beginning with $:/ which are optionally hidden from view and edit templates, but certainly will not come up in the sidebar search.* *An added feature of the extended field naming in 5.2.0 is designers and developers can use fieldnames with their own prefix eg I use $:/psat/tiddlername I can also use $:/psat/tagname so it would be nice to use $:/psat/fieldname* I also had a previous request that I thought was being implemented, that resulted in this https://github.com/Jermolene/TiddlyWiki5/pull/5315 I hope it can proceed. This may also be related https://github.com/Jermolene/TiddlyWiki5/issues/1324 Regards Tones On Thursday, 17 June 2021 at 01:12:19 UTC+10 Mat wrote: > Just thinking out loud... > > As you may know, the coming v5.2.0 will feature unrestricted field names. > This is very big news! This will push fields to a substantially more > prominent position because *fields can then be directly mapped to > tiddlers*. I mean, just look at this: > > *"In the current tiddler, get the values of the fields with names that > match a filtered set of tiddler titles." * > > \define getdata() {{$(curr)$!!$(field)$}} > <$vars curr=<<currentTiddler>>> > <$list filter="...filteredtiddlers..." variable=field> > <<getdata>> > etc > > So, the field values could be a relationship between the current tiddler > and those other tiddlers. For example: > > title: Adam > Barbara:mother > Caesar:father > David:friend > > ...or from the other direction, i.e *"In a filtered tiddler list, get the > values from the field(s) named as current tiddler"*: > > <$vars curr=<<currentTiddler>>> > <$list filter="...filteredtiddlers..." variable=field> > <$transclude field=<<curr>>/> > etc > > Another use: *"Transclude the content of a filtered set of tiddlers using > templates. But which specific template is used depends on the relation the > tiddler has with the current tiddler"* > > \define getdata() {{$(tid)$||$(template)$}} > <$vars curr=<<currentTiddler>>> > <$list filter="..." variable=tid> > <$vars template={{{ [<curr>get<tid>] }}}> > <<getdata>> > etc > > ...so, for example, if the relationship with current is "closest family" > then apply the template that also shows a photograph. > > Here the "getdata" macro only does a template transclusion but if the > field values contain complex data such as "Queen Elizabeth: sister queen > [[pole dancer]]" the macro could of course do much more complex stuff > treating such values as flags or variables etc. > > > IMO the next bottleneck related this matter, are tools for controlling > field values. One such discussion is CheckboxWidget - generalize to also > toggle individual items #5613 > <https://github.com/Jermolene/TiddlyWiki5/issues/5613> > > <:-) > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/18be46dd-6383-4574-ac1a-db11dbeba713n%40googlegroups.com.
