Si, and Folks, Interesting thread with some very interesting information and techniques.
Si Asked > I wonder if anyone has done something similar, or has a different approach > worth sharing? I understand the issues with alternative triggers and Eric was wise to keep the dirty method hidden, however I believe we need to extend functionality where possible, it can be done with with guidance and caution. Because this is all so dependant on triggers I want to restate an Idea, I had some time a go and still intend to demonstrate, but the simple idea is to allow additional actions to be set for any existing trigger in tiddlywiki. The most common triggers are of course buttons. Buttons are triggered to save, close and edit, they can be used to save the wiki and reload, and many more functions. Often when trying to solve a problem with a trigger one (or more) of the existing buttons may actually fulfil this role. So given these various timers and triggers it may be quite easy to leverage existing buttons or the action navigate to trigger a timer action (conditionally). One thought was to try and identify the missing triggers, for example a logout button that saves and resets the user would also be a suitable time to do "on exit" triggers, other on exit actions can be loaded on top of it, perhaps like backing up the content of local storage to file. Or my interest is check in on single file wikis. An on exit trigger is the complement to the existing startup actions as they are for "on wiki load" trigger. Building a set of available buttons that by definition are used in the user interface at the practical occasions where we often need a trigger. If we introduced a set of timer buttons, or a timer utility where you could set on off or reoccurring timers then enabled custom actions to be triggered 90% of all the timer trigger needs would be met. This tool can be designed to stop infinite loops as much as possible so the tools given to the user are not fragile. As has being illustrated in this thread, date or period elapsed triggers are another desirable feature, This is a kind or raw functionality we should provide if not in the core in a key plugin. A generic non specific solution. One reason it should be provided upfront is it can be made efficient by cascading the test, on change in month we can test for a change in year, and at no other time except load. The most tricky is change in day (midnight when wiki is still open) Regards Tony On Sunday, June 21, 2020 at 10:08:10 PM UTC+10, si wrote: > > I use TiddlyWiki as a task manager, among other things, and I thought it > would be cool to know how long I spent working on a completed task. > > Off the top of my head I imagine having a "start/stop" button that will > alternately add a timestamp to the fields "start" and "stop". Then I could > (hopefully) create a macro that calculates the total time spent on the task. > > I wonder if anyone has done something similar, or has a different approach > worth sharing? > -- 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/e4da9a6e-770e-4200-9992-b594c378a913o%40googlegroups.com.
