Hi Devin, > Also I had thought that the core rendering engine would delay reactions to > storage changes till next tick allowing changes to finish and the call > stack to exhaust. That way multiple changes to a tiddler only trigger a > final DOM render. Does the system not do this? Seems that would be a huge > performance issue if it attempted to update the DOM at every step of the > call stack. >
That's correct. I imagine the impact here being rather negligent, performance-wise. The only option would be to copy the logic which IMHO is worse then storing > twice. Keeping the two in sync would be a nightmare. Keeping track of and keeping up with core changes would indeed probably be a challenge / source of plenty issues. I presume you did some testing as to check if your code actually works. I think I'm inclined to update tobibeer/appear to incorporate the refactoring. Well, will have to do tests anyway. Ok, if I leave a mention for *@sukima* in the version history? Best wishes, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/8d2333f7-0c31-4cbb-acfd-e852ab5e9088%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
