<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Oh, I see! When I started reading what you said, the idea of integrating your caching strategy within the framework popped in my mind and I couldn't see anything else for a while. It is true, what you actually suggested is completely different. Still, the general solution to allow a lot of VectorGraphics stuff to be usable right now would be a great thing to have. Let's keep thinking and discussing this for a couple of days before choosing an approach. Cheers, On 6/19/2020 11:59 AM, Hilaire Fernandes via Cuis-dev wrote: <blockquote cite="mid:66f38630-3fc1-16e8-3c67-ae7d7c2e7f45@drgeo.eu" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> In DrGeo canvas (with Pharo's cairo canvas), I don't use cached forms, the whole canvas is top down re-draw when marked dirty. Brutal but a long time ago I discovered that in this specific situation it was much faster rather than Morph update mechanism based on dependencies. In some DrGeo canvas you can have a lot math items (models). Each model is rendered as a morph in the canvas, it eases the debugging as you can inspect a faulty item with the help of the halo. Not sure it is the right way to go for a more general approach, but a dedicated PasteupMorph will clarify how ones can write a small interactive application. Not sure I was clear. <div class="moz-cite-prefix">Le 19/06/2020 à 16:42, Juan Vuletich a écrit : </div> <blockquote type="cite" cite="mid:5EECCEE6.3070807@jvuletich.org"> You mean making your caching strategy part of the framework? Sounds like a good idea, and not too hard to do (you already did the work). Still, Morphs would need a message to invalidate the cached Form and redraw it again with VectorCanvas, right? Right now, you are caching 2 Forms, but a genera framework solution should allow easily invalidating the cached form without needing to know how many variants could exist, and what triggers the change. This is getting really interesting. Let's move it forward!</blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire">https://pouet.chapril.org/@hilaire</a></pre> </blockquote> <pre class="moz-signature" cols="72">-- Juan Vuletich <a class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a> <a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a> <a class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a> <a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a> @JuanVuletich</pre> </body> </html>