These are chat archives for ractivejs/ractive

14th
Jan 2019
kouts
@kouts
Jan 14 09:43
Hello all and happy new year!
I'm thinking of giving a presentation about Ractive on my local devs group
kouts
@kouts
Jan 14 20:44
I would ideally like to keep it simple and around 30', any suggestions on topics that I should focus?
Brandon
@twisterxiz_gitlab
Jan 14 21:39
Hey everyone, I had a quick performance question that I'm trying to figure out if anyone had a minute
Brandon
@twisterxiz_gitlab
Jan 14 21:53
First off I'm working on a older repo using ractive v0.8.15. Basically we're implementing a new feature that does a real-time duplication of the text field, kindof like a WYSIWG editor. The property being duplicated is only referenced twice on the input field and in the template reference to show the text, however when it is updated it makes every other reference in the template dirty and essentially rerenders most of the page taking up to about 200ms per key stroke. We've never had a live update requirement before so the initial 200ms page load was pretty much unnoticeable, but for this new feature we definitely need to reduce this time down. This is a very large template and I've verified that I didn't have any computed properties or anything that would cause this, it's purely a volume of computation issue. Is there a way I can indicate to ractive that not every property on the parent object needs to be reevaluated or is this a limitation to the dirty checking mechanism and templating engines in general?