gonnavis

// Processing code by Etienne JACOB
// motion blur template by beesandbombs
// opensimplexnoise code in another tab might be necessary
// --> code here : https://gist.github.com/Bleuje/fce86ef35b66c4a2b6a469b27163591e


int[][] result;
float t, c;

float ease(float p) {

gonnavis

// by Etienne JACOB
// motion blur template by beesandbombs
// needs opensimplexnoise code in another tab
// --> code here : https://gist.github.com/Bleuje/fce86ef35b66c4a2b6a469b27163591e

int[][] result;
float t, c;

float ease(float p) {
  return 3*p*p - 2*p*p*p;

gonnavis

// Processing code by Etienne JACOB
// motion blur template by beesandbombs
// opensimplexnoise code in another tab might be necessary
// --> code here : https://gist.github.com/Bleuje/fce86ef35b66c4a2b6a469b27163591e


int[][] result;
float t, c;

float ease(float p) {

gonnavis

TOTALLY SUPER DUPER NOT MY WORK! Trying to illuminate how FizzyText (seen here, source here, isolated from dat.GUI dependency here) works. Original appears to have been written by George Michael Brower.

In the original, which I find brilliant:

• Solid black text is drawn onto an invisible canvas, from which it gets bitmap data
• The bitmap data is read like a collision detection array, where black means "you're on top of text" and white means "you're not"
• Particles of size r=0 are randomly spawned on a visible canvas
• The particles grow if they're on top of a (non-rendered) black pixel, and shrink till they disappear if not
• When they shrink to r=0, they respawn randomly somewhere
• The particles follow a Perlin noise flow field, a very sensible and fluid kind of random movement, in which nearby particles