Distorted Android

Postprocessing buffers mBuffer[] are now shared among all postprocessing operations. This saves a lot of memory, but also means that when doing each particular postprocessing, the textures backing up the mBuffer might be too large. We need to fix two things here: when outputting to those too large textures, we need to adjust the Viewport, and when binding those too large textures as input - we need to adjust the TexCoords to compensate....

SSBO: now we have a more-or-less correct running average of the count of transparent fragments over the last few frames.

SSBO: correct various things.

SSBO: handle the fact that we might run out of space in our SSBO if we keep creating new Surfaces.

SSBO: counting of transparent fragments more or less works now. Still the counters are zeroed out in the wrong place - every time we start rendering something to a given Surface, rather than once per frame.

SSBO: more and more works...

SSBO: something is working already, although we still get the 4 bytes back from the shader in reverse order ( so '17'=0x00000011 written by the shader becomes '285212672 = 0x11000000' )

First try at the SSBO (doesn't work - reads in the application don't pick up changes in the shader; crashes.

Simplification in PostprocessEffects

Move all the knowledge about Vertex and Fragment effects to their respective classes.