Hi Saq, would it be an option for Streams to set "open" nodes into TW's draft-Mode? Thinking a little more about the problem, Soren's idea is maybe worth to think about closer.
Regards, Mirko [email protected] schrieb am Mittwoch, 26. Mai 2021 um 09:28:41 UTC+2: > Hi Mirko, > > Yes, i'm using Streams 0.2+. When typing on >> https://saqimtiaz.github.io/sq-tw/streams-tiddlytoolmap2.html it "feels" >> also relatively lazy when typing fast, but there you have a huge stream >> (much much larger than my ones). Console states for my browser (FF) between >> 150ms and 240ms mainRefresh for each keystroke (which is a lot when you >> type fast) at your toolmap. >> > > I intentionally use that wiki to test for performance issues as they get > amplified due the size of the stream. With smaller streams there are no > noticeable delays when typing. So if your own streams are much smaller, > then there has to be another reason that the performance is so much slower. > > >> In my wiki (aaldrich-tables in combination with content-nodes based on >> your streams-plugin) i have ~500ms mainRefresh for each keystroke... as it >> is not that easy to give my wiki away atm, i will first investigate a >> little on my own regarding your "vars/set/wikify widget"-hint, which i >> definitely have within my structure... >> > > If you inspect the DOM structure of the streams in the web developer tools > and see that they blink/refresh on every keystroke, that is a very good > indicator that something in your widget tree causes everything to be > re-rendered on each key stroke. You will notice that this does not happen > when using Streams on the toolmap wiki or on the Streams demo site. > > When a variable set by the vars/set/wikify widget changes, that widget > needs to remove and re-render all its children for them to be informed of > the new variable value. > > >> Anyway would it be nice to be able to disable the TW5-rerendering >> (temporarily) globally. i will open a feature request. >> >> > One hack here would be to write a widget that you wrap your templates in, > which does not refresh its children. Note however that such an approach, or > any approach that disables refresh, opens the door for data loss. > > Regards, > Saq > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/948d64ca-c3a0-4309-9726-b3675192fbf6n%40googlegroups.com.
