On Monday, May 24, 2021 at 7:13:04 AM UTC+2 Mat wrote: @pmario - Haha! Thanks for taking the time with screenshots etc which of > course also teaches me (and others) how to use that tool. I'm assuming that > the time is measured from the back of the blue and that "double height" > means "double time", right? >
It's the DOM structure that we see here. So every layer shows a dom element and its child elements. The higher the "bar", the more DOM elements need to be handled. Since the TW core has to "calculate" which elements have to be redrawn, it also show a little bit of the "complexity" and the "connections" between the elements. ... BUT it's not directly related to the time that is needed. But what can be seen in the first image is, that the sidebar calculates more more elements as actually shown on the screen. ... > But what does it mean that the, say, search field is slower than > everything else? > I think I didn't say that. I only wanted to explain some "landmarks", so you can connect the images to the rendered page. I didn't want to say, that it is slow. ... It probably isn't, since it's only 1 element with several child's. So looping through them should be reasonably fast. Is the whole page not useable before the search bar is fully loaded? I.e is *all > *frozen? > As I wrote. The map only shows the dom structure and has no direct relation to the time needed. -mario -- 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/48cf31c8-a616-45af-9237-bd96b3290613n%40googlegroups.com.
