I like that plan! I understood previously that you had plans for a small series of quicklets or what ever name you would give a collection. The fun part is, that other people can add to that and we could end up with a nice collection of small and easy - but useful tiddlers.
@TW_Tones, I donāt think the thread was hi-jacked. Rather that, inevitably, the topic falls between semantics and technical operations. One personās checklist is anotherās vague probing. What is my point? Merely that that checklists could be a (1) list of definitive directives, or series of prompts (2) probing the netherverse.
I very much appreciate your overall intent. I think the central issue is that the ācontentā of items varies between āclosed / definitiveā and āopen / vague rambling probingā. TBH, checklists, in general, are seriously under-theorised as both open and closed mechanisms.
The content of items can matter.
Not wishing to throw a spanner into the works. But worth saying, I think.
TT, x
My attention was drawn back to this thread due to someone liking a post. I thought I would just mention some possibilities given the updates of late or pending to tiddlywiki.
As at the original post we can make use of the template cascades to have tiddlers parsed differently like the original Quicklist idea.
We could store the todo items as titles in a single list field, especially in TW 5.2.3 with the new Checkbox widget listField parameter.
I would like to release a series of quick, in tiddler, solutions but unfortunately have other ālife issuesā to deal with. I may return here and post a quicklist update.
There is an edge case where tw5-checklist works wrongly!
Try to create a checklist with two similar entries like
[ ] Milk
[ ] Milk
[ ] Bread
Of course this is an edge case. I have the same issue in Shiraz quick table (task list example )
The reason is the check/uncheck action uses a global search/replace
I also enjoyed tw5-checklist and found that issue, unfortunately Iām not skilled enough to know if what Iām about to say would help or not, but if it relies on a global search and replace, couldnāt the plugin wrap the corresponding text with spanās and give them uniquely generated ids? maybe using the date created, down to the second?
Just food for thought, Iām sure there are better methods out there to resolve it, Iām personally pretty sad that itās no longer being updated and whatnot.
Hi Justin,
Have you submitted a ticket on GitHub? The plugin is in JS and I cannot debug it. But to be honest this edge case is very rare in real life!
So, enjoy it!