On Sunday, 6 January 2019 12:05:02 UTC+1, tony wrote: > > On Friday, January 4, 2019 at 1:25:19 PM UTC-8, Joe Armstrong wrote: >> >> >> It seems to me you can come a long way with tags and filter operations >> over tags. >> > > Indeed! That is why your re-implementation of Chandler is a breath of > fresh air. > > My needs are simple and expedient. I've moved back to analog with the joys > of a fountain pen and paper to more rapidly capture daily tasks. >
Yes :-) As regards the automation of simple tasks I've been doing some experiments. I had some tiddlers tagged 'draft' and 'final' then I made a button to change draft to final - the problem was that now I could do this operation too quickly - in order to change draft to final I needed to read what I had written and *think* - the *deliberate* act of adding a new tag and removing an old one slowed things down. Automating this meant I could do the operation faster than I could think - also automation added a layer of unnecessary complication - the power of the system came from the filter operations over tags and not the ability to automate tag manipulation. Deciding how much to automate is a very tricky problem and needs several rounds of prototyping to get it right. Personally I favor the idea of a minimal viable program (see https://joearms.github.io/#2014-06-25%20Minimal%20Viable%20Programs) I'll have to implement the ticket system I described above in the TW :-) Cheers /Joe > > I still believe in a simple hyperlinked plain CamelCased wiki > <http://wiki.c2.com/> as a repository for my stuff not as a Jira or Trax > replacement. > > For me, not every wiki entry is/needs the UI widget baggage polluting the > text area since the wiki is not the end product, but a means to externalize > memory in plain text. > > If tasks and projects are important enough I add them to my TiddlyWiki and > then archive to VimWiki <https://github.com/vimwiki/vimwiki> which is > better cross platform. > > Plus I'm intellectually too impatient and lazy to learn more TiddlyWiki > tinkering. I'm still learning the command line. > > Too much friction leads me to abandonment. [1] > > Chandler provides the convenience of separating actionable items from rest > of the wiki. This is why a simple semantic tag, 'chandler' is so powerful. > It separates my wiki into actionable and not actionable stuff much like > sparse trees and agenda in OrgMode <https://orgmode.org/> > > >> So what does your new ChandlerDone look like? - I'm curious >> > > Chandler's dashboard reminds me of Korsakov's LinearHomeoscope > <https://en.wikipedia.org/wiki/Semyon_Korsakov#Inventions> where adding > another Archive 'pin' to ChandlerDone 'search' > > <$button> > <$action-sendmessage $message="tm-add-tag" $param="archive"/> > <$action-sendmessage $message="tm-remove-tag" $param="done"/> > <$action-sendmessage $message="tm-remove-tag" $param="chandler"/> > {{$:/core/images/chevron-left}}archive > </$button> > > results in returning the done actionable items back into the broader wiki. > > Essentially in GTD <https://gettingthingsdone.com/> speak back to > supporting notes. > > And what of tiddlers that need to go back to the Chandler dashboard, like > say recurring action items? > > We can retag with 'chandler' and 'now' > > I added a ChandlerizeButton tagged with > $:/tags/ViewToolbar > > as outlined in Customise TiddlyWiki > <https://tiddlywiki.com/#Page%20and%20tiddler%20layout%20customisation> > > <$fieldmangler> > <$button> > <$action-sendmessage $message="tm-remove-tag" $param="archive"/> > <$action-sendmessage $message="tm-add-tag" $param="chandler"/> > <$action-sendmessage $message="tm-add-tag" $param="now"/> > {{$:/core/images/star-filled}} > </$button> > </$fieldmangler> > > and added its button title, > {{ChandlerizeButton}} > > to position it accordingly in the ViewToolbar > > TiddlyWiki's powerful search will recall past archived projects and tasks > and I click the star ChandlerizeButton to add it back to the Chandler > dashboard set to my Home button. > > This allows simple movement of entries in and out of Chandler completing > the triage loop and system for me. > > Since there is date stamping [2] for plain text future proofing, a > calendar is extra frosting! > > Thanks again, Joe > > Best, > tony > > [1] The TiddlyWiki Classic (TWC) past was glorious and littered with > TiddlyTasks TogglyTagging siglets CycleTags > <http://coloredlinks.tiddlyspot.com/#CycleTags> and endless tasting of > all this generous group has to offer. Eric L Shulman's TiddlyTools > <http://tiddlytools.com/> was a fount of tinkering tools, but with great > power, comes great responsibility. > > Imagine having to maintain this in 5, 10, 20 years? > > Over time I found the need to switch back to simplicity like evil org-mode > adding deft <https://jblevins.org/projects/deft/> then finally settled on > VimWiki <https://github.com/vimwiki/vimwiki>. Investing in time tested > tools like bash, emacs and vim has been fruitful plus CodeMirror bindings > in TiddlyWiki for vim and emacs means old tricks still work for this old > dog. > > [2] I like literal hard coding for future proofing thanks to Riz's date > stamp button > <https://groups.google.com/d/msg/tiddlywiki/UHt6GsMpyAQ/USFJxw68AQAJ> on > my Editor toolbar, I can log entries and recall with simple search inside > or outside of TiddlyWiki > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/37f0a9d3-2d2b-4735-bc3f-1203e97205c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
