Hi there,
A few words about TextureClient/Host (since it's been mentioned in this
thread):
we have a bit of design doc about it at:
* http://dxr.mozilla.org/mozilla-central/source/gfx/doc/MozSurface.md
* http://dxr.mozilla.org/mozilla-central/source/gfx/doc/SharedMozSurface.md
Basically TextureC
Thanks for the detailed reply. I never expected that Servo would be able to be
able to avoid the possibility of concurrent access to surfaces, for a lot of
those same reasons that you mention.
I have a few questions about the docs.
1. What copy-on-write optimizations is this referring to?
"* W
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
ContainerLay
3 matches
Mail list logo