That's a good point about texture caching. But I don't think that there are any advantages to painting in the compositor. Painting and layout are both off the main thread in Servo, so nothing will block the main thread either way. We cache display lists in the painting thread in Servo, so there's no need to go back to layout if the animation is compositable. And as roc mentioned in Portland, it's important to keep the compositor as lean as possible.
Patrick On Sun, Mar 22, 2015 at 4:28 AM, Nicolas Silva <nical.si...@gmail.com> wrote: > Another thing worth thinking about is to have some of the animated > content rendered directly in the compositor without being stored in a > layer. The Blink folks have a project along these lines. If we know that > the portion that is animated is simple enough that we can render it at > 60 fps, caching it in a texture at the layer level is just wasted cycles > and memory. > > Cheers, > > Nical > > On Sat, Mar 21, 2015, at 07:27 PM, Patrick Walton wrote: > > Hi everyone, > > > > I've been thinking about ways that Servo's architecture can result in > > user > > experience improvements in common Web patterns today. > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
