Question #176657 on Graphite changed: https://answers.launchpad.net/graphite/+question/176657
chrismd proposed the following answer: I'd say its partially fixed with rev 591 in that the reflowing of the page is fixed but the waiting for the next render part isn't. The way to fix that is to preload the graphs on each refresh in hidden <img>'s then after each one renders, replace the previous <img> element and unhide the new one. The reason that's not as easy as it sounds to actually implement is because Ext currently does all the dom dirty-work via its DataView widget, and the refresh methodology I described is not compatible with how DataView works (it iterates a bunch of records and instantiates a template for each one and assembles all that into a chunk of dom thrown in the page). Basically the auto-refresh functionality will have to be separated from the DataView.refresh() calls that are necessary when the store records change, and the auto-refreshes will have to operate on the <img> elements in place. It's definitely possible, but not trivial. Patches whole-heartedly welcomed :) -- You received this question notification because you are a member of graphite-dev, which is an answer contact for Graphite. _______________________________________________ Mailing list: https://launchpad.net/~graphite-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
