Olli Etuaho

Events like EventHideEvent and BufferRemoveEvent aren't really the same thing as the events that make up PictureBuffer contents. Consider storing them in a different array inside PictureBuffers. This might make...

The color space of the picture color values should be defined. There could be options for blending in linear or perceptual space.

This becomes necessary to manage GPU memory usage as the layer count and/or size of the picture increases. So it's readPixels time!

This could be faster since texSubImage2D doesn't need to do as much error checking. Alternatively could try using uniform arrays.

Adding a script for compiling the unit tests along with the code would be the most obvious idea. The unit tests integrate with the code so tightly, that only compiling...

The library should be able to determine when undoing a buffer removal becomes unlikely enough that the memory for the removed buffer can safely be freed. Freeing could also be...

Out-of-sequence undo for move events doesn't produce very good results yet. One reasonable goal for out-of-sequence undo would be that the following sequence would not change the picture: 1. Move...

This would improve robustness of the code. Asserts offered by the Google library would probably be the best choice, since the library is already written with Closure compiler in mind.

This would be useful for multitouch applications. Basically, the currentEvent could be replaced with an array of events, and Picture.setCurrentEvents() added beside Picture.setCurrentEvent(). A multitouch example could be built on...

This type of vertex shader code failed to render a vertical gradient, which is why the current code generates different shaders for vertical and non-vertical gradients: if (abs(uCoords0.x - uCoords1.x)...