Rework throttled refresh

[BurningTreeC]

This PR reworks the throttled refresh so that it works for the styleRefresh, too.
It adds two switches so that we can control if we want only the styleRefresh to throttle or only the mainRefresh to throttle.
It also makes the styleRefresh in new Windows equal to the styleRefresh in the main window.
Also in new windows the throttling is added, the same way as in the main window.

[github-actions]

Confirmed: BurningTreeC has already signed the Contributor License Agreement (see contributing.md)

[BurningTreeC]

This now works and deferres the changes for both styleRefresh and mainRefresh in both the main window and new windows

[BurningTreeC]

@Jermolene @pmario @saqimtiaz here's a build with performance instrumentation enabled:

https://rework-throttled-refresh.tiddlyhost.com/

[pmario]

... here's a build with performance instrumentation enabled:

Seems to be slightly faster than the tiddlywiki/prerelease

[Leilei332]

Actually I wonder why opening $:/TagManager and $:/Manager is especially slow when there are many tiddlers or tags.

[BurningTreeC]

Actually I wonder why opening $:/TagManager and $:/Manager is especially slow when there are many tiddlers or tags.

Hello @Leilei332 - do you notice this in general or in this PR?

[Leilei332]

Actually I wonder why opening $:/TagManager and $:/Manager is especially slow when there are many tiddlers or tags.

Hello @Leilei332 - do you notice this in general or in this PR?

This is a general problem in tiddlywiki. In this PR it is a little quicker.

Tag Manager (PR):

performance: styleRefresh: 8.00ms
performance: mainRefresh: 1103.00ms

Tag Manager (prerelease):

performance: styleRefresh: 13.00ms
performance: mainRefresh: 1122.00ms

Manager (PR):

performance: styleRefresh: 17.00ms
performance: mainRefresh: 513.00ms

Manager (prerelease):

performance: styleRefresh: 16.00ms
performance: mainRefresh: 514.00ms

[Leilei332]

I think the two tiddlers should be improved because its performance is slow on mobile phones. The result is the same (performance in this PR is a little faster than prerelease)

This PR:

Prerelease:

[Jermolene]

Thanks @BurningTreeC this is promising, but I don't think we're ready to include it in v5.3.6.

One issue is that the code of render.js is now pretty gnarly and hard to follow. I think we need to consider refactoring the rendering and refreshing into a generic class that can be used both for styles and body content. In a separate branch I've been exploring the idea with a new "wikifier" class. See this commit. It will need to be extended to allow it to replace all the occurrences of rendering/refreshing in the system.