Greatly expanded the Readme, proving a decent explanation for all the various projects in the repo.

Also simplified the code for the GreenFlyingDot project, and added a small comment to MiniFade.
Added a small physics simulation sketch. A bouncing LED that matches (or should match) a bouncy ball on a solid floor.
Renamed the sketch from Bouncing.. to BouncyBallPhysics.
Updated readme to reflect name change.
Updated code to do all calculations in meters per second and using kilogrammes and the like.

The serial interface now accepts kinetic energy changes in Joules, in the direction of travel. Negative force can change the speed down to a minimum of zero, reversing the moving ball requires a little more code to check current direction, energy and the like.
BouncyBallPhysics documentation updated.

Explained limitations and a bit more on the working of the sketch. Added a gravity constant for the moon (commented) and cleaned up a few minor parts of the code.
Complete rewrite of BouncyBallPhysics.

Rewrote the core of the BouncyBallPhysics sketch to a Ball class rather than just a struct to hold the data. This allows all the movement to be handled by methods of the ball, gravity working on it and the ball moving as a result of it. This allows for many falling and bouncing objects to be processed on the strip.

Additionally, the code that handles the bounce has been improved to calculate the exact moment of the bounce, placing the ball in the correct spot after the bounce (with the correct speed and direction).

Some additional cleanup and rewriting needs to be done to complete the class. There also needs to be a slightly better color management, as multiple balls are difficult to separate from each other at the moment. A color that changes intensity seems likely.
Cleaned up BouncyBallPhysics sketch

* Removed deadspeed global as it's no longer necessary, everything comes to a halt naturally;
* Kinetic forces given over serial can only be positive, removed the check for '-' char for Serial.peek();
* Ball class Constructor that sets height can now also set a speed (defaults to zero);
* Renamed several methods to names that fit better to the physics they describe;
* Changes of velocity because of acceleration are handled through direct speed adjustments, not as added kinetic energy;
* Bouncing a ball no longer removes a static 1 Joule of energy from the ball, only elastic losses apply.
Fixed support for negative gravity

A bug in timeForDisplacement caused bad results with negative acceleration, causing a square root calculation with negative input. This has been fixed, which resolves #1.

Also added a postBounceLimitCheck() that, when the ball has come to a stop places it on one of the edges of the strip and faces it in the correct direction. This resolves #2.

An array for ball colors has been added, and replaces the calculated color of the balls dependent on their speed. This makes it easier to keep the different balls apart as they bounce along the strip.

Wrapped all serial debugging prints in precompir #if statements, causing them not to be printed during regular operation. Added a function to the serial interface whereby sending a '?' reports the height, speed, and kinetic energy for all the balls.
Fixed timeForDisplacement where acceleration == 0

This _actually_ resolves #1 (the previous commit only fixed the negative gravity case, not the negative gravity

Also swapped a number of duration,acceleration arguments, the duration coming first and the acceleration second. Renamed the 'accelerate' method on the ball to 'travel' that takes an optional acceleration argument, the default of which is zero. Zero gravity simulations now work properly :)
Fixed bug with reversed arguments to displacementAccelerated()

Also set the update interval to 3 milliseconds as the Arduino seems incapable of keeping up with three balls on a 2 millisecond interval. Will need some performance tweaks to achieve higher precision / more balls on the strip.
Fixed last timeForDisplacement bugs

Function no longer requires absolute values for acceleration and displacement. The correct values are passed in and calculated. Directions on the strip have been changed so that balls going up have positive speed. This makes the new-height calculations more intuitive to interpret.
Expanded BouncyBallPhysics documentation.

Also changed the starting height of one of the balls so that they don't overlap initially.
Added color blending where balls overlap

This resolves #3.
Merge pull request #2 from edelooff/master

Update Frack repos to latest from origin