Hi Ton, Just to clarify, are you suggesting that when the end date field is missing from a tiddler then it should default to the current date?
If so, I would rather not default the end date to the current date, as this would mean it would be given a value for the timeline when the end date was missing in error, which could lead to confusion. I would rather have the error reported. However, although it isn't something I need, perhaps it would be useful for others. So what I could do is allow the end date field on a tiddler to contain the word 'now' and I would then fill in the current date/time. This would mean an end date would be mandatory (if endDateField attribute is on the plugin call), but you would fill it in with 'now' if you want it to roll forward. Let me know if that would help and I can look at coding/testing/documenting this weekend, Martin On Friday, 14 March 2014 16:06:15 UTC, Ton Gerner wrote: > Hi Martin, > > As already mentioned by me, it is nice and easy to use. > > Playing around with it I used: > > > > <$visjstimeline filter="[tag[test]]" startDateField="start" > endDateField="end" format="YYYYMMDD"/> > > Then I came across the situation with a timeline starting in the past and > still going on (current date). > > When I did not fill in the endDateField, I got an error: Not a endDate () on > ... > > Looking at the documentation of moment.js I found: > > To get the current date and time, just call moment() with no parameters. > > So it looks like it is possible; be aware I am not a programmer ;-) > > Is there a trick to make the end = current date? > > Cheers, > > Ton > -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
