[squeak-dev] On the performance of our browsers... THEY TICK!

tim Rowledge tim at rowledge.org
Sun Jan 21 18:46:59 UTC 2018


A lot of Morphs simply fetch & re-render new info at every tick (or at least, they used to). For some case that is actually proper (think Dave N Smith’s ancient crawling BlobMorph). 

Some got a bit smarter and at least compared the new info to the old before rendering new stuff. Of course, sometimes that involves comparing something a bit more complex than a 10 character String, so not all that smart. And sometimes even simply fetching the new info involves proxies transforming into large amounts of data obtained fro a slow server somewhere, or a colossal list being pointlessly rebuilt.

Getting everything up to date and using #changed etc so morphs only update when they plausibly need to would be a nice thing for slower machines like Pis. We’ll need to have something that considers all the browsers to be its dependents so that when a code change is made that would affect a browser other than the active one we can have the change broadcast to everyone properly. And it would be nice for it to be able to be pretty specific about the change so something a bit more efficient than ‘redraw everything’ can be used. The current CodeHolder>>#updateCodePaneIfNeeded and CodeHolder>>#didCodeChangeElsewhere arrangement doesn’t look particularly nice. 

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: MAW: Make Aggravating Whine




More information about the Squeak-dev mailing list