I support your idea! Related information is better to be kept in one single tiddler specially when these information are small! Having a lot of tiddlers, tags, fields makes confusion, increase entropy of system and normally difficult to maintain and are more error prone.
In few of plugins I used data tiddlers and it results to much compact, better to follow and understand structure. --Mohammad On Monday, August 19, 2019 at 5:18:25 PM UTC+4:30, PMario wrote: > > Hi Folks, > > The whole discussion was probably started by a PullRequest > <https://github.com/Jermolene/TiddlyWiki5/pull/3971>, that I made some > time ago. > > It is about a new filter operator named: keyvalues. We do have indexes > and getindex which allows a "list-widget" to list all indexes or to read > a defined value. Using those operators you need a nested list-widget, if > you want to list both: the "key and the value". > > That's why I did create the operator. Usage examples can be seen at an > example > wiki > <http://3971.tiddlyspot.com/#keyvalues%20Operator:%5B%5Bkeyvalues%20Operator%5D%5D%20%5B%5Bkeyvalues%20Operator%20(Examples)%5D%5D>. > > > > The suggestion at the moment is, to implement it as a plugin. ... Which I > am considering. ... > > In the PR Jeremy pointed out, that handling many small tiddlers is the > same as handling 1 bigger one. .. From a program point of view this is > right. ... From a users point of view I think it isn't. > > As Hubert pointed out in the OP, he doesn't want to use plugins. But if I > do create a lot of related tiddlers, where some of them are system > tiddlers, users need a specialized UI to export / import different states. > ... If there is no UI users can't reliably handle a given state. > > If the "given state" is saved in 1 data-tiddler that's a simple exercise. > > So IMO there is a usecase for data-tiddlers. An other example: > > Let's say I have a sudoku game UI, which consists of 9 x 9 fields, which > results in 81 cells. That's OK for most users, for 1 sudoku. > BUT every cell has 9 helper-cells, which gives us max 729 tiddlers. > > In my special case the game field is 11 x 11 (sandwich sudoku), which > gives us: 11 x 11 x 9 = 1089 tiddlers. ... That's OK for me as a > programmer, but if I need to transfer or save a special state, its close to > impossible for a user to save without a specialized UI. > > At the moment I do create 121 tiddlers per game, and I think that's > already too many. ... Especially, since 1 TW will / can contain many > different games. > > Game initial settings and game-states should be easy to save and reload. > Unlimited "Undo" and "Redo" is essential for a sudoku. So data-tiddlers > allow me to bundle information, because it belongs together. > > Just some thoughts! > > have fun! > 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/13d0e1ff-7935-4732-905f-040b420b3c35%40googlegroups.com.
