On 06/30/2014 10:14 PM, Cameron Zwarich wrote: > We discussed this a bit on #servo, but it isn’t obvious from your > diagram if every Layer will have child layers, or if that will be > reserved for specific container layers.
The way I've designed it now, TileLayers are not siblings of ContainerLayers, but are instead data members on ContainerLayers. All ContainerLayers can potentially have children, but none of those children will be TileLayers. > CoreAnimation takes the former approach, but I think the latter might > be more applicable for Servo, since it would give a better separation > of concerns. We would then have the following layer types: > > 1. ContainerLayer, which can only parent other layers. 2. TileLayer, > which would manage tiling, BufferRequests, and all double buffering > of individual tile backing stores. 3. TextureLayer (maybe ImageLayer > would be a better name?), which is backed by a simple image. Would we > even want it to be double buffered? I still need to look a lot more closely at how tiling works in the next phase, but this design works for me. I think most of the pieces are already in place actually. --Martin _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
