As a long-time member of the The 5,000(+) Tiddler Club, I’m always trying to reduce lag in my (often complex) wikis. I prefer Zoomin mode in any case, and I’ve historically used it in combination with solutions like the Dynaview plugin and @Yaisog’s SingleTiddlerView (which I still appreciate, but doesn’t play well with my custom page template).
It occurred to me today that the simplest way to make Zoomin truly single-tiddler might just be to restrict the list filter in my story template to… a single tiddler. Here’s the code I’m currently using in my equivalent of $:/core/ui/PageTemplate/story
:
<div class=StoryRiver>
<$scrollable class="tc-story-river">
<$list
filter="[[$:/HistoryList]get[current-tiddler]] :intersection[list<tv-story-list>] ~[list<tv-story-list>first[]]"
<!-- ^^ filter="[list[$:/StoryList]]" in the default story template, for reference -->
history=<<tv-history-list>>
template="$:/core/ui/StoryTiddlerTemplate"
storyview={{$:/view}}
emptyMessage={{$:/config/EmptyStoryMessage}}
/>
</$scrollable>
</div>
So far, this has been working wonderfully and I haven’t experienced any issues. It’s a very simple substitution—I just tested my filter in the core PageTemplate/story and it works just as well there. It’s blazing fast, and it preserves the animated transitions, for those who care about that sort of thing. But it seems almost too good to be true, so I wanted to run it by the experts here. Can you see any potential problems I’ve overlooked?