Hi @Yaisog, I’ll take a look, but it probably won’t be until tomorrow at the earliest.
- Long borders are outside the borders
- I migrate all tiddlers from $:/plugins/yaisog and $:/core/modules/filters/format/timestamp.js but nothing appears when I save.
Hi @moosh, you probably need to activate the PageTemplate first: Press Ctrl-Shift-L and select the new PageTemplate. Alternatively, select it in ControlPanel → Appearance → Layout.
I really do need to add a short description of how to install it in another wiki, or alternatively package it as a plugin…
Regarding the linebreaks, go to ControlPanel → Appearance → Theme Tweaks, and set “Wrap long lines in code blocks” to “Yes”.
Have a nice day
Yaisog
It was enabled, apparently the problem is in the browser, since is displayed normally in Firefox.
Is it possible to enable the ability to save revisions to other buttons? For example, to the add comment plugin Mehregan — personal knowledge management app
It makes sense to make it possible to add a short description to the revision, which will be displayed with the name in the viewer.
Hello @moosh, the creation of revisions is done by calling the global macro make-incremental-backup
with the title of the tiddler to be revisioned as a parameter, e.g.
<$macrocall $name="make-incremental-backup" title=<<currentTiddler>> />
This can be added to any button, to be performed on-demand.
It makes sense to make it possible to add a short description to the revision
You mean like in e.g. a code commit or a manual snapshot? That’s a slightly different application from what I had in mind. I don’t think it would take a lot of work to change the macros and templates to add this, but it would be another plugin with a different purpose? It would probably require some tweaking at other ends, e.g. the prune-backups
macro should never prune manually created revisions, and these should also be visually distinguishable in the list.
While I currently have no plans to add more functionality beyond the basics on the proof-of-concept site, I might pick up on the idea at some point. But, like with all things TiddlyWiki, it is possible for anyone to just take my code and extend it.
Hi @Scott_Sauyet (and maybe other), there was a typo in $:/plugins/yaisog/ui/PageTemplate/MessageHandler/tm-save-tiddler
that led to unexpected behavior when deleting fields. This is now corrected on the demo site.
Again, amazing work. I’m not quite sure where I will want to use this yet, but I simply know I will.
One bug: there seems to be a mismatch between what’s reported in statistics and the number of revisions shown on the viewer.
Hi @Scott_Sauyet, regarding the bug: The viewer always also shows the current state of the tiddler, which in most cases is not a revision (unless you go back to an older revision, then a copy of the current state is made beforehand). There is a note at the top when viewing the current state:
I did think about showing only “current” in the list instead of the full date, to make it clearer, but then I thought that knowing the last modification date of the tiddler might also be beneficial. I can see how this would be a little confusing, though.
Maybe I’ll put the last modified date into the explanatory note…?
I don’t know if I was stuck in some old version by accident or in some intermediate state. The issue I was seeing is totally gone and everything seems to be working the way I’d expect.
I don’t know when and where I’ll use this (most of my main TW work is on Node and Git; where I already have a useful versioning mechanism) but I do know that I will be using this at some point. Thanks for the useful tool!
@Yaisog
In JD’s revisions plug in, the revisions are shown in the tiddlerinfo tabs.
Is it possible for your implementation also?
Hi @arunnbabu81, I’ll have a look, but cannot promise anything regarding timeframe or even implementation.
There is no urgency from my side. Take it as just a suggestion.
Can you add also a whitelist of tiddlers to keep patches for (and not to keep for others)? This would be great for me as I’m a bit hesitant to keep patches for every change I make but there are some tiddlers where this is important for me (and having to keep deleting patches for all others is a burden)
@arunnbabu81 @Ittayd
I just uploaded an update that should include both of your suggestions.
The revisions are now shown in a tab of the info area. This can be toggled via the ControlPanel settings page.
The settings page now also contains a whitelist editor. The whitelist, just as the blacklist, works as a filter, i.e. to only back up tiddlers in the $:/plugins/yaisog namespace, you would replace the universal default [is[tiddler]]
with [prefix[$:/plugins/yaisog]]
. The blacklist is applied after the whitelist, if you wanted to fine-tune the selection.
Have a nice day
Yaisog
PS: Please note that I also updated the wiki to v5.3.5, so that the custom $:/core/modules/filters/format/timestamp.js override is no longer needed, and I replaced the $:/plugins/yaisog/macros/friendly-date-subfilter with a JavaScript version $:/plugins/yaisog/modules/filters/userfriendlydate.js that implements the same functionality in a custom filter operator.
I just noticed starting at the bottom of the revisions list, you can also move up and forward in time to see the tiddler content evolve.
Couple issues I found…
- Click the edit button then…
- Click on the Revisions button, then the More options button…
Thanks for the heads-up.
No. 1 was a result of a messed up offline upgrade to 5.3.5. After a full re-upload everything should be OK now.
No. 2 was a side effect of sticky titles and lazy code re-use. Now fixed.
Have a nice day
Yaisog