Eric,
Looks good and very professional. You have addressed a serious gap in
tiddlywiki capabilities through this set of solutions. For the community I
thought I would provide some suggestions why I think this is a Big step;
- Tiddlywiki has now increased the usable time date resolution to
seconds (or less), perhaps before it was good for history and task
management now its good for time management.
- This allows time of day planning, event reminder and popups giving
the "time of day" part of calendars, thus calendar events.
- Time triggered events now allow an alternative trigger that does not
demand a user trigger, this means new forms of automation are now possible
that were not so easy, and at a minimum, needed a plugin to be developed
for a specific purpose.
- Solutions with Reminders are now much more feasible
- With timed "events/actions" a TiddlyWiki can produce meaningful
results without any user interactions
- With TiddlyDesktop this can include triggering processes on the
computer
I hope other that are inspired also share what they can get from your
solution.
Thanks very much Eric.
Tones
On Sunday, August 9, 2020 at 10:40:35 AM UTC+10, Eric Shulman wrote:
>
> Update August 8, 17:22pm (PDT): http://TiddlyTools.com/timer.html
>
> * There are a number of significant changes in this update:
>
> 1) TiddlyTools/Timer/AnalogClock and TiddlyTools/Timer/DigitalClock has
> been combined into TiddlyTools/Timer/Clocks
> 2) This new combined Clocks tiddler no longer uses "templated
> transclusion" (e.g., {{||TiddlyTools/Timer/AnalogClock}}) to embed a clock
> in a tiddler.
> 3) Instead, the new Clocks tiddler defines a <<clock>> *macro* that can be
> used to embed either the analog or digital clock.
> 4) This macro also includes parameters for specifying the timezone
> "offset" and an optional "format" override for the digital clock.
> 5) The SidebarClock and WorldClocks tiddlers have been updated to use the
> new <<clock>> macro instead of transclusions.
> 6) The WorldClocks tiddler has also been updated to provide a multi-select
> list for choosing which places to display.
> 7) A new tiddler, TiddlyTools/Timer/Places, has been added to define the
> list of available places for use with the WorldClocks tiddler.
>
> Documentation for all of the above changes in syntax and usage have been
> updated in TiddlyTools/Timer/Info.
>
> Note that, while these changes do not alter the overall functionality,
> they do make usage and customization easier and more consistent
> by using macro parameters to control clock options, rather than defining
> "context variables" to pass those values to the underlying code.
>
> Hopefully these changes don't cause too much grief for anyone who had been
> using the previous version...
>
> Please let me know right away if you run into any problems with using this
> update.
>
> enjoy,
> -e
>
>
>
>
> On Wednesday, August 5, 2020 at 8:38:39 AM UTC-7, Eric Shulman wrote:
>>
>> update August 5, 08:30: http://TiddlyTools.com/timer.html
>> <http://tiddlytools.com/timer.html>
>>
>> * AnalogClock/DigitalClock - handle leap years in "days per month" (dpm)
>> calculations in adjustForTimezone()
>>
>> <$vars leap={{{ [<yyyy>divide[4]split[.]count[]match[1]then[yes]] }}}>
>> <$set name="dpm" value="31 28 31 30 31 30 31 31 30 31 30 31"> <!--
>> days per month -->
>> <$set name="dpm" filter="[<leap>!match[]]" value="31 29 31 30 31 30
>> 31 31 30 31 30 31" emptyValue=<<dpm>>>
>>
>> Be sure to update before the end of February 2024 (the next leap year)
>> This will be accurate until the year 2100 (which is NOT a leap year)
>>
>> -e
>>
>
--
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/63d1337c-9624-444a-8c65-eec711c6d120o%40googlegroups.com.
