Mathias Agopian 49457ac092 Encapsulate textures into their own Texture class ... the main reason for doing this is so that we can have access to informations about a texture (like its dimension) close to where we generate and use shaders in ES 2.0. Previously, there wasn't any way to get to a texture's size from a RenderEngine implementation. Bug: 8679321 Change-Id: I388b338a70d07e3e8177dde248710ea1e4c82dff		2013-08-16 16:29:02 -07:00
..
Description.cpp	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
Description.h	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
GLES10RenderEngine.cpp
GLES10RenderEngine.h
GLES11RenderEngine.cpp	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
GLES11RenderEngine.h	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
GLES20RenderEngine.cpp	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
GLES20RenderEngine.h	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
GLExtensions.cpp
GLExtensions.h
Mesh.cpp	don't reallocate the mesh each time we use it	2013-08-13 20:51:23 -07:00
Mesh.h	don't reallocate the mesh each time we use it	2013-08-13 20:51:23 -07:00
Program.cpp	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
Program.h
ProgramCache.cpp	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
ProgramCache.h
RenderEngine.cpp	Fix ES2 composition on some devices	2013-08-15 14:56:51 -07:00
RenderEngine.h	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
Texture.cpp	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00
Texture.h	Encapsulate textures into their own Texture class	2013-08-16 16:29:02 -07:00