Compositing over WebGL: Must repaints be scheduled? about zebkit

[barmalei]

The idea of doing repainting asynchronous is improving zebra painting performance. During event handling, component hierarchy validation multiple repaint method calls can occur. But all of them just update dirty area and trigger (if it has not been already triggered) repainting thread (well, thread is not a very good term in the case of JS).

Regarding repainting customization. You can try to replace "window.requestAFrame" with an own implementation. The method is called by zebra paint manager to trigger re-paint thread. The method gets function that actually has to be called to do the real painting. Sort of:

window.requestAFrame = function(f) {
     f();
};

For more deep repainting customization you can write an own paint manager and configure it via "zebra.json".

[joeedh]

I actually added an immediateRepaint to PaintManImpl (rather hackishly; I just shove it into PaintManImpl.prototype and zebra.ui.paintManager).

I do think this should be configurable, or at least more flexible.

[joeedh]

Also, any way clearRect could be called when updating or removing window components that don't have a zebra element behind them? I have my own hackish solution, but something better would be nice.

[barmalei]

I am not aware too much about what you are doing with painting, but have doubt that immediatePaint will does repainting more effective than postponed repaint. Also don't understand what you mean with "should be configurable or at least more flexible", "Also, any way clearRect could be called when updating ..."
?

[joeedh]

Basically, the delayed paint causes flickering. This could be related to my second point, that the canvas behind windows isn't cleared when moving them (not if there isn't another visible zebra component behind them, at least).