On Wednesday, June 16, 2021 at 5:12:19 PM UTC+2 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
>
It will be hard to create an efficient algorithm with this setup, in
wikitext. You have 2 variables here.
- The field name
- The field value
As a developer you neither know which "name" a user will use and you don't
know the values which are used. .. So how do you want to create an
algorithm?
You need a configuration tiddler somewhere. .. This problem has been the
same for ages.
So having "freeform" field names alone won't solve any of the problems you
describe here. .. In the contrary. It will open up new problems and edge
cases, that we don't even know yet. ...
just some thoughts
mario
--
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 protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/f6eb47e7-c59e-4272-b7f4-78b2acc288b7n%40googlegroups.com.
