Yes, I have seen that, thanks. Unfortunately, I lack the necessary skills/time to identify the pieces that would need to be adapted to allow for viewing (and updating) a running overview of the task status for the last 10 days.
On Saturday, August 14, 2021 at 10:04:33 AM UTC-7 saq.i...@gmail.com wrote: > This is one of the first things that came up with a search, perhaps it may > be of interest: > https://rawgit.com/Guitlle/habito/build/build/habito-docs.html > > On Saturday, August 14, 2021 at 6:54:23 PM UTC+2 Saq Imtiaz wrote: > >> Just to add a bit more clarification to the issue since I have a bit more >> time now than I did yesterday, this functionality should have been >> implemented as a widget and not a macro. I quickly dropped the link in >> reply yesterday so you would know that there was some follow up on your >> post. >> >> JavaScript macros in TiddlyWiki5 are supposed to be for simple text >> substitution and do not have any facilities for refreshing in response to >> other changes in the wiki, the input of the macro determines the output. A >> macro should never modify tiddlers. The macro in question both needs to >> refresh itself in response to tiddler changes, and also modifies tiddlers. >> >> Such a macro was never intended to be supported but has worked so far >> because we were aggressively refreshing entire tiddlers when anything in >> that tiddler changed. So for example a change to a tiddler "list" field >> would refresh the entire tiddler in the story. However this is suboptimal >> both from a performance point of view and in terms of user experience. Some >> of the annoyances commonly encountered like an edit-text widget in a >> tiddlers text field not being usable to modify a field in the same tiddler >> come from this aggressive and unnecessary refresh behaviour. >> >> So the question that presents itself now is whether we maintain backwards >> compatibility for a behaviour from third party macros that was never >> intended to be supported and holds back improvements, or break such macros >> as their implementation will trip us up again in unexpected places and >> limit future possibilities. >> >> Your actual need for the functionality offered by this macro could >> probably be solved with a wikitext implementation as well. It might be >> worth a search to see if someone has shared such a solution. >> >> Regards, >> Saq >> >> On Saturday, August 14, 2021 at 6:42:38 PM UTC+2 cmari wrote: >> >>> Thanks Saq, that was certainly not the answer I was hoping for, but it's >>> good to know which way the wind is blowing after so many years (I think the >>> original dailytasks plugin that got me started 13 years ago came from you?). >>> cmari (considering changing my name to "offspec user"!) >>> >>> On Friday, August 13, 2021 at 1:03:59 PM UTC-7 saq.i...@gmail.com wrote: >>> >>>> See >>>> https://github.com/Jermolene/TiddlyWiki5/issues/5903#issuecomment-898691487 >>>> >>>> On Friday, August 13, 2021 at 9:26:33 PM UTC+2 cmari wrote: >>>> >>>>> I have been a happy daily user of *Daily Task Macro *( >>>>> http://togglers.tiddlyspot.com/) for years, so I am wondering whether >>>>> someone can point me to any tips for how I might update the macro so that >>>>> it will continue to work in the new prerelease. >>>>> >>>>> Specifically, the fields in toggler tiddlers do continue to update >>>>> correctly when the images are clicked, but the (svg) images themselves do >>>>> not update in response to the click until the tiddler is opened and >>>>> closed >>>>> again. >>>>> >>>>> Thanks for any help! >>>>> cmari >>>>> >>>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d907a01f-a345-475a-b627-619c204575b8n%40googlegroups.com.
