While it might be used as a rough approximation of the document.lastModified
value, the modification timestamp of the last tiddler change is NOT the same as the timestamp of the file itself. Consider: suppose I make a tiddler change to a local TiddlyWiki file and save that file, and then several hours (or even days) later, I upload this file to a server (e.g., TiddlyHost). The timestamp of the online file will be dramatically different from the modification timestamp of the last tiddler change.
Note also that your suggested filter can be written much more succinctly, like this:
[all[tiddlers]get[modified]!sort[]first[]format:date[DDD, DD. MMM YYYY]]
Notes:
-
There is no need to sort the tiddler TITLES. We only need to sort the actual modification timestamp values.
-
The !
preceding the sort[]
filter operator sorts in reverse (descending) order… and since the modification timestamps all use TWCore 17-digit fomat (YYYY0MM0DD0hh0mm0ss0XXX
), the default alphanumeric sorting is sufficient, without need to do any date conversion preprocessing before sorting.
-
The first[]
filter operator isn’t strictly needed, since the filtered transclusion used as the text=...
parameter value in the $text
widget will always return just the first resulting list item. However, it is still useful in that it avoids extra format:date[]
processing overhead for all the other modification timestamps.
-e