Mohammad, Personally I feel we have all the possibilities available to use already.
- However I must ask where are you wanting to use state tiddlers? I ask because arguably they usually relate to an open tiddler, but then if you want to toggle states one or more transclusions deep or in a macro unless you make use of the currentTiddler/storyTiddler something else is needed. In relation to a recent post by you I went off working on bringing my tiddler serial number tool to the point of publishing. I bet you did not realise you often influence hours of work on my part. Unfortunately I have not finished it because there are some other pre-requisite changes that will make it far more professional (Custom actions for buttons). I also have other work today I must complete. *Let me commit to the end of the week for this TSN solution. * A Serial number, allocated automatically and/or only when needed allows you to create state tiddlers of the form "namespace/#/item" eg "$:/colors/2314/background" which could contain the background color for the tiddler with the serial number 2314. The serial number will be created and stored in the tiddler and will work regardless of what it is named in the future. The advantage of this is the serial number is always unique unlike a tiddler title which is only unique at this point of time. Any prefix + a serial number is a unique tiddler. Personally I have discovered a wide range of opportunities using serial numbers, I call them TSN's as Tiddler Serial numbers #tsn one example is; - Have another form of shadow tiddler for any desired tiddler eg $:/shadow/#tsn in which a field that matches that in the original tiddler may contain a tooltip for that field in the original tiddler. - Given the power of unique serial numbers other interesting ideas include a "virtual" word based serial numbers to generate/enforce unique variables or macro names. - I also have a method to apply serial number without touching the tiddler, useful for core/shadow tiddlers which we do not normally rename anyway. As usual my problem is too much coffee and too broad an imagination Regards Tony On Monday, February 10, 2020 at 11:14:40 PM UTC+11, Mohammad wrote: > > Refereeing to recent discussion on The Good and Bad of qualify: > https://groups.google.com/d/msg/tiddlywiki/51XMzmLGxfQ/PLkfWWthBAAJ > > We know many cases in creating User Interfaces (UI) needs some state > tiddlers. > > I got used to call qualify for such cases, but with the recent discussion > it seems qualify is NOT designed for purposes one like to keep some states > permanently and irrespective of current tiddler situation. > > Mat proposed a slugify operator > <https://github.com/Jermolene/TiddlyWiki5/issues/3379#issuecomment-505042751>. > > Also the Mario unique ID plugin is a potential tool here > > > My question is: > > Is there any other ways to create unique stateTiddler? I dont mean do this > manually? > > > There are situation, one needs permanent state tiddler to keep data. For > example in Shiraz dynamic table I uses state tiddler to keep footer data or > row styles. > These are not temporary data and it is tedious to define unique state > tiddler for every table! > The current mechanism I use is qualify macro which is not good for all > scenario. > > > --Mohammad > > > p.s: > One KISS solution is to use a helper function which calls now macro > with [UTC]YYYY0MM0DD0hh0mm0ssXXX format to create a unique title for the > required state tiddler. > > -- 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/ef11875f-d974-46e0-b21d-be216fef1e74%40googlegroups.com.
