Hey all, I’d encourage anyone building this kind of tweak (that is, a way to include system tiddlers in the recent tab, or a system-specific recent tab), to do TWO more things:
(1) simultaneously do the same for system TAGS (either toggle the tags tab to include system tags, or enable an additional More tab focused on system tags). I imagine having them toggle with the same button would be intuitive – at any given time, one either is in system-tinkering mode, or one is not.
(2) include a note in your solution demo about the ReadOnly css that would be helpful for anyone with a front-door (public) vs back-door (author) interface.
For the initial OP solution by @twMat here, the simplest ReadOnly css companion seems to be:
.recentsys-icon * {display: none;}
(Of course, that’s assuming the state is a temporary one – you don’t want your public viewers to load the page with the system stuff stuck in the on position!)
UPDATE: Ideally, someone ( ) would build a version of the button by @twMat that would toggle the inclusion of system tiddlers across a wide range of places where we might look for them.
Meanwhile, I tweaked my tiddlyhost demo site with versions of the additional More tabs in the @DaveGifford style (with fix noted above):
- added SysRecent tab (with list-after:$:/core/ui/MoreSideBar/Recent)
- added SysTags tab (with list-after:$:/core/ui/MoreSideBare/Tags)
… and then realized that @Mohammad’s Node Explorer is another resource that does not (out of box) include system tiddlers, but where one might want to toggle system results into view temporarily while in system-tinkering edit mode.
(As a quick solution for myself, I just hacked Node Explorer for now. A toggle-them-all solution in the style of what @twMat did in the OP would take a bit more time, but would be fantastic: Basically comb through for all the GUI nooks and crannies that include a [!is[system]]
string in a filter, and wipe out that specification…)