In other systems data tiddlers (or their equivalents) are a foundational aspect of their design. Not so in TW. In TW data tiddlers are just a stop-gap, a convenience tool to be used in a limited set of circumstance. For instance, note that JSON data tiddlers can only go one level deep.
Try doing anything more than very simple data referencing, and you'll find that there are very few filter operators that work with data tiddlers. For instance, there is no filter operator to obtain all the values of a data tiddler. In TW, the fundamental data structure is the tiddler. There are lots and lots of filter operators that know how to deal with tiddlers and tiddler fields. Data tiddlers are meant for simple one-to-one lookups, like with the color palettes. Beyond that and they become too onerous to work with. On Monday, April 12, 2021 at 6:44:44 PM UTC-7 [email protected] wrote: > G'day, > > I'm just curious about the experience-based philosophies out there. > > Personally, I have a preference for indexes (and data tiddlers), reserving > fields when a data tiddler is overkilll (more work than it is worth.) > > How about you? When do you prefer using indexes (and data tiddlers), and > when do you prefer using tiddler fields ? > > -- 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/f70bd7e8-1ebd-4171-9371-10c7461d31d9n%40googlegroups.com.
