On Wednesday, May 5, 2021 at 9:22:04 AM UTC+2 Mohammad wrote: > On Wed, May 5, 2021 at 11:10 AM Saq Imtiaz <[email protected]> wrote: > >> True for all fields. A field is changed by creating a new Tiddler with >> the same fields (including title) and updating the necessary field when >> creating that new Tiddler. > > > I did not know this! So, tiddlers are immutable is a correct sentence! Is > this the best way from performance point of view? >
Editing internal memory would be faster, but it also creates some tricky problems. ... In TWclassic it is possible to directly change "portions" of a tiddler from a plugin. The core sometimes doesn't see these changes. So it doesn't trigger a refresh cycle. The plugin author has to trigger the refresh cycle. But the plugin author doesn't know, if a full or partial update is needed. So the common practice in plugins was to always trigger a full refresh cycle, just to be sure, that the core _and_ all other plugins see it. This behavior wastes much more performance as creating a new tiddler does in TW5. In TW5 there is no other way to change something, without the core knowing about it. So the core tells every plugin, what happend. I hope that makes it clearer. have 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/88d29df4-22f0-46b3-9623-b9126e6c6016n%40googlegroups.com.
