Distorted Android

Fix a long-standing buf in CubesGrid (incorrect Grid in case of 5x5 11111 11011 10101 11011 11111)

Chasing a bug in DistortedCubesGrid.markRegions() ( visible with a 5x5 grid, 11111 11011 10101 11011 11111 ) - some side edges are missing. markRegions computes incorrect number of side Segments in this case.

Various relatively minor cleanups.

1. (hopefully) finish the 'Save' app (now we can adjust the size of the resulting file)
2. Fix one long-standing bug in almost every single app.

Move the 'Save' app to using a DistortedFramebuffer.

Improvements for DFramebuffer.

Fix the 'Save' app so that the saving thread does not run all the time in a tight loop

Javadoc

Fix with Projection

Turn the former 'FOV' app into 'Projection' app that also checks the (x,y) the camera looks at.

Javadoc

Move the *List classes into static members of DistortedFramebuffer and DistortedObject.

Javadoc

Cleanup

Cleanup

DistortedFramebuffer should we working now, including deletions.

Cleanup

Simplify SurfaceViews

Move DistortedNode and Distorted to use the new DistortedRenderTarget.

Minor progress with RenderTarget

New DistortedRenderTarget - preparation for being able to render to any FBO (screen, offscreen pixmaps)

Minor stuff

Minor stuff

Fix the 'Save' app on Android API >=23 (we need to explicitly ask for write permission)

Minor stuff

Add 3rd dimension to the Deform effect.

Improve the Deform app

DEFORM: add support for Regions

Polish up DEFORM.

re-write the deform effect

rearrange comments

rearrange comments

Merge remote-tracking branch 'origin/master'

1. Conflicts:
2. src/main/java/org/distorted/library/EffectNames.java

Allow more than the default number of concurrent VERTEX and FRAGMENT effects in Effects3D.

New vertex effect 'PINCH'

Complete moving center to 3D.

Make the effect Center be always 3D.

Unify Effects3D and Matrix3D (still incomplete!)

Encode more info in the EfectNames enum.

Progress with WindManager.

Dynamics: Introduce 2 Modes of operation:

- 'random access' mode, where we are able to call a single Dynamic from multiple thread simultaneously.
- 'sequential' mode, which only permits sequential interpolation from one client.

The second mode has an advantage when one needs to change mDuration: it keeps on interpolating smoothly. In the first mode, this is not possible.

2 bugfixes:

- in Dynamics, it has to be t<=0.5 (rather than t<0.5) (see comment in code)
- in EffectQueueVertex, we need to postprocess() the last time, when effect is finished but not removed!

Minor details

Progress with Wind

Tidy up 'Cubes' app

Bugfix

Bugfix (sometimes, when t=0.5 exactly, it wouldn't recompute Noise in case of PATH mode)

re-generate noise after passing each Point.

Flag app finished

Next fixes for issues with 'jumping' path when noise is on. (and a whole lot of commented out debugging)