The quickest and easiest ever todolist in tiddlywiki ? Requires 5.2.0

#12

Mark,

Yes part of the Quick here was making it not just its use. I already have thoughts on resolving the “potential” field pollution problem but it certainly raises again something I mentioned before the 5.2.0 release, the concept of a system field namespace.

However one mitigating fact with the current quicklist may be its purpose, a quick list on any wiki to collect thoughts, actions etc…, once completed it can be moved, deleted or exported and the new fields go with it.

Thanks for the suggestion.

Yes, well actually I am tempted in a later release to move from a simple check box because there may be value in having different content in this field. If you have created a tiddler from one of your todo lines it may change to “externalised” (for want of a better word).

I am tempted to apply a prefix or suffix to each field and filter them out of the drop down, then the pollution is much reduced. Being able to filter out fields from the drop down would be a good core hackable.

As @Birthe intimated it is possible to run down rabbit hole with anything in tiddlywiki. Although this example is generating some innovative ideas I also see value in applying a whole lot of constraints. New ideas may form a subsequent solution rather than change this one.

It is now possible to more easily extract and delete lines from text, but there are no mature solutions for this. I think if the item is externalised (with the + button) and tagged with the current tiddler I could delete the line, and field and list here via the current tiddler tag. Think of the quickllist as a scrap of paper, you dispose of rather than keep indefinitely.

#13

<<storyTiddler>> is effectively an alternative to currentTiddler, it is set in the view template process (where I found it) as it iterates the items in story list. In a way, by never changing its value in my own code (unlike currentTiddler in lists etc…) it becomes a reliable alternative for the tiddler title you are looking at. I write all my code for currentTiddler where possible. Other related tricks are possible with the <<transclusion>> variable.

#14

You don’t actually change the value of TW’s “currentTiddler” when you create a list. You’re creating a new variable, called currentTiddler, scoped to the list.

Throw this at tw.com:

<<currentTiddler>>

<$list filter="[tag[HelloThere]]">

:<<currentTiddler>>
</$list>

<<currentTiddler>>

So, inside the list rendering, you can think of currentTiddler as “private” to the list widget.

#15

That is correct!

As they get more complex like using multiple transclusions or macros that use macros it is good to have each macro respond to currentTiddler, rather than demand a tiddlername be provided.

To follow your example;

<<currentTiddler>>

<$list filter="[tag[HelloThere]]" variable=additional-tag>

:<<currentTiddler>> <<additional-tag>>
</$list>

<<currentTiddler>>

In which case <<currentTiddler>> remains the original tiddler.

The final code pattern used here is when you don’t need the value of the filter.

<<currentTiddler>>

<$list filter="[all[current]tag[HelloThere]]" variable=nul>

:<<currentTiddler>>
</$list>

<<currentTiddler>>
#16

Hi Mark, I have a fix for tw-checklist. Coupled with autolist mod and a toolbar icon + keyboard shortcut, it is quite fast. No field or tag pollution. Ping me if of interest. It is not packaged.

1 Like
#17

@fastfreddy [tw5] Re: editor-auto-list - how to add [ ] to * and # - this was very useful.

#18

What is autolist mod?

Thanks!

#19

Hi Mark!
This is a small mod to Saq’s autolist plugin that makes it effective for the check list input format. This is the mod: https://talk.tiddlywiki.org/t/tw5-re-editor-auto-list-how-to-add-to-and/1102

In my workflow (beyond the Autolist mod mentioned above), I have fixed a minor functionality issue in tw5-checklist itself, and I added an option in the configuration tiddler to hide/show the input form. Together with a toolbar button/keyboard shortcut, the checklists behave like numbered or bulleted lists during input.

#20

I appreciate everyone cross referencing other checklists, but this thread has being hijacked.

I would liked to have discussed the original idea rather than all its alternatives.

In future feel free to mention other solutions but please start your own thread and link to that as well in the same reply (edit later if necessary).

My own thoughts on the original quicklist here is as follows;

  • Create the fields with a prefix such as $:/local/ item content
  • Exclude “system fields” or [prefix[$:/local/]] fields from the new field dropdown
  • make a “quicklist” tiddler just one of multiple types of tiddlers that have a different viewTemplate handling. In this case it simply turns each line / list item into a line with a checkbox.
  • I plan to use the object-type field to select from different viewTemplates and hide the existing $:/core/ui/ViewTemplate/body
  • this generic solution would allow us to create a whole range of different tiddlers that respond differently to the content of the text field.
#21

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.

Thinking hat on - and off to play.

1 Like
#22

@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

1 Like
#23

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.

Eg with listField requires 5.2.3+

<$list filter="[all[current]object-type[quicklist]]" variable=~>

   ;Quicklist tiddler
   <$list filter="[all[current]get[text]splitregexp[\n]]" variable=each-line>
	    <$link to=<<each-line>>/><br>
			<$checkbox tiddler=<<currentTiddler>> listField=done-items checked=<<each-line>> unchecked=""  > <<each-line>></$checkbox>
	 </$list>
</$list>
  • In a tiddler tagged $:/tags/ViewTemplate

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.

1 Like
TW 5.2.3 is Getting Ready to Be Released
#24

@TW_Tones Thanks for your updates. I liked your post today when I try to search a solution to quickly add a todo list for daily journal.

My user case is that I create a daily Journal tiddler to plan a to do list with checkbox in the morning, then can check a item to mark it as finish.

#25

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

2 Likes
#26

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.

#27

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!

#28

I have not, since it isn’t actively supported anymore, and honestly, I wouldn’t know how to word it anyways :sweat_smile:

#29

I will submit a ticket!

See [BUG] Duplicate Items Causes Checklist Works Wrongly · Issue #51 · tgrosinger/tw5-checklist (github.com)

#30

I tried this here in its original demo and Do not see any fault with duplicate entries?

  • Also I updated that wiki to 5.2.2 and still no problem I can see.
1 Like
#31

Thank you Tony! Yes this version works fine!