All 4 of these are kind of the same feature in a way: Save a tiddler while editing, without jarring interruptions. When they are apart, the issue is not resolved.
Honestly, I believe this is the single biggest issue with TiddlyWiki usability right now.
As I describe at the end of this post, the scrolling issue is the key deeper problem. The rest of these features can be done with relative ease. But the scrolling issue holds all these things back.
Larger Feature Set
- Save While Editing
When a tiddler is in edit mode, press a save button. The editor stays open, and the scroll position is not lost (or it is recorded, and returned to when quick-saving the tiddler)
- Maintain/Restore Scroll Position After Saving
Approach 1: suspend all scrolling until after the tiddler re-opens
Approach 2: save the editor cursor position to restore the scroll position
Approach 3: save the original tiddler without effecting the “Draft of” Tiddler
- Sticky Editor Toolbar Option
Examples of this feature look and work seemlessly with the right styling
(Also: this includes the edit mode save/close buttons)
- 2 Toolbar Buttons: Take and Restore a Tiddler Snapshot
Even a single snapshot (per tiddler) would make the more frequent saving, safer.
A snapshot (clone) gets saved to a system path that can be cleaned out.
Keeping it at 1 snapshot reduces bloat, but is still effective at facilitating more frequent regular tiddler saves.
Because there is no dropdown, it’s just one click to take a snapshot, and 1 click to restore it. Taking another snapshot replaces the last one.
There would need to be a method for deleting snapshots from the same system location en-masse in the Control Panel.
Scroll-Freeze Justification
The scrolling issue all by itself is the big one. It’s a JS issue. Perhaps it could be a module. But it seems a good candidate for a primary functionality. (I’m getting better at TiddlyWiki, but I am a long way from being a JS dev.)
After fixing the scrolling, something like the EditButtons plugin makes a lot more sense, as do these other features.
Scroll-Freeze Feasibility
I would assume the scrolling is a theme-specific issue (because some themes have multiple rivers etc.), but that it would require making the river’s JS/CSS cursor position available to the theme more generically.
Freezing all scrolling is an acceptable “loss” until TW is done saving and/or re-opening the tiddler if that be the case. This only occurs when that type of save button is pressed - the one that keeps you in the editor.