Confirmed users
138
edits
Platform/GFX/textures: Difference between revisions
→Textures and Compositables
No edit summary |
|||
| Line 75: | Line 75: | ||
A compositable pair (client & host) manages one or several textures and implements the logic side of things (such as double buffering or producer/consumer models). There should be different compositable implementations for the different strategies. | A compositable pair (client & host) manages one or several textures and implements the logic side of things (such as double buffering or producer/consumer models). There should be different compositable implementations for the different strategies. | ||
To give an analogy with android's SurfaceTexture, CompositableClient should be the equivalent of ANativeWindow, and a | To give an analogy with android's SurfaceTexture, CompositableClient should be the equivalent of ANativeWindow, and a given implementation of TextureClient would be the equivalent of SurfaceTexture and implement the same producer/consumer model, while TextureClient/Host operate at a lower level to just abstract out the type memory (since the multiple backends require us to support more than just EGLSurface). | ||
== Migration to the new textures (Meta bug 893300)== | == Migration to the new textures (Meta bug 893300)== | ||