Jan,
I see you had an example
1789-07-14
Quick example
\define indate() 1789-07-14
{{{ [<indate>split[-]join[]] }}}
gives 17890714 <https://tiddlywiki.com/#17890714>
But try
\define indate() 1789-07-14
{{{ [<indate>split[]!match[-]] }}}
{{{ [<indate>split[]!match[-]join[]] }}}
So a lot can now be done with raw wiki-text although you will often find
you need a button to trigger saving a field etc...
Regards
Tony
On Monday, 24 August 2020 00:15:02 UTC+10, Jan wrote:
>
> Hello everyone, hello Eskha in particular...,
>
> Two years ago I asked two questions about the vis.js-timeline
>
> -Could we get the plugin to parse more than one date format? For example
> in my usecase there is exact dates and timespans where exact dates are not
> appropriate (Like the Renaissance or so)
> -How can I enter dates BC (before Christ)?
>
> I just searched my inbox and I found your hint which has slipped through
> my attention. Thanks a lot, this works!
> Am 24.10.2018 um 20:38 schrieb Eskha:
>
>
> Hoping this may still help you for your second point: I use "Y" format for
> date and a "-" in front of the date (eg -200 for 200 BC
>
>
> This already helps a great deal, but I still would like to parse / enter
> different date-formats to the plugin. I ask myself, whether i could replace
> moments.js which is can render hundrets of formats by something smaller and
> more tolerant to enter the dates. Can anyone say how the date is
> transferred from the moments.js-widget to the timeline?
>
> More tolerant means that it would replace 1789-07-14 by 1789 vice versa
> without causing an error.
>
> Best wishes
> Jan
>
>
>
>
>
--
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/bb7d2364-3a71-468f-930f-c684b6f7f3e1o%40googlegroups.com.
