One thing to bear in mind is that the core has always supported unrestricted fieldnames for almost all operations. The primary thing that's changing now is that the switch to the JSON store area allows us to guarantee that arbitrary fieldnames will be respected over a save-and-reload cycle. The secondary thing is the removal of the very weak protections against creating fieldnames containing arbitrary characters.
Perhaps there a relatively small number of usecases for complex fieldnames, but some of those use cases are powerful and so seem important. But even in the absence of important use cases, a very important benefit is that unrestricted fieldnames make TiddlyWiki significantly simpler to explain. Every little arbitrary restriction or caveat adds to the conceptual load for people learning TiddlyWiki. For me, one of the most important consequences is that we can encode variable name/value pairs as fields. For example, in the new publishing framework that is under development we represent a publishing job as a configuration tiddler that specifies the template to be used, the filter identifying the tiddlers to be output, and a collection of variables to be provided to the rendering. The variables are expressed as fields named "var-foo", where "foo" is the name of the variable, and the field value is the value for the variable. It's a simple and flexible approach that wouldn't be possible without loosening the restrictions on field names. Best wishes Jeremy -- Jeremy Ruston [email protected] https://jermolene.com > On 17 Jun 2021, at 10:42, Mohammad Rahmani <[email protected]> wrote: > > Like Mario, for me it is not clear what will be the benefit to have such > liberty in naming fields! > I think Tiddlywiki is growing organically! Sometimes you need to see good and > consistent logic to be able to write better code to understand and maintain! > So, while I am not against the new feature in TW 5.2.0 but I really like it, > we are going toward a more consistent, easier to learn and easier to maintain > grammar and syntax! > > > > Best wishes > Mohammad > > >> On Thu, Jun 17, 2021 at 11:27 AM PMario <[email protected]> wrote: >> Let me be more specific eg: >> >> >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 >> >> You mentioned that having upper-case letters in the field names can help to >> solve the "relationship problem". .. >> >> I ask: Where is the difference from a setting below and your suggestion? >> >> title: adam >> barbara: mother >> caesar: father >> david: friend >> >> There is no difference. The setting in the example has been there since >> v5.1.0 .. and the problem isn't solved. ... >> So as I wrote: Having more possibilities in the field names won't solve >> anything. Sorry. >> >> -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/9663224c-7512-4bba-a424-decf876dc943n%40googlegroups.com. > > -- > 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/CAAV1gMDRxgAA8pZ1nnY56j34uTqw1ux8%2BX0gkqDTcSK-LPkX-g%40mail.gmail.com. -- 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/FEB2B99E-6A23-42E8-A8B4-5B7A03670E83%40gmail.com.
