26-AUG-2025

1313

I think I need to focus on building a separate svg renderer that does a better job of separating the update/render stuff. The SVG widget should basically first-and-forget the SVG render, and the update should look it up after. Probably the ‘simplest’ way to do that is to hash the SVG Template after compiling the template, and have the renderer cache based on that hash. I’d push the template.render() step up to the update call, then on the render call look up based on the current hash – so that I don’t clone the png data, I just retrieve an ARC to it from the renderer.

1313

I think I need to focus on building a separate svg renderer that does a better job of separating the update/render stuff. The SVG widget should basically first-and-forget the SVG render, and the update should look it up after. Probably the ‘simplest’ way to do that is to hash the SVG Template after compiling the template, and have the renderer cache based on that hash.