shows a problem with the smooth saddle approach. The max and min are no longer all at points. The smooth saddle approach adds no additional points at a saddle point and this causes problems with the example data.

Conflicts:
	curvedLines.js

Return "empty array" rather than "null" if data is missing

"series.datapoints.points = null" can cause other parts of flot to crash

However, testDate still doesn't work because you get the error 'Uncaught
Error: Time mode requires the flot.time plugin. '.

auto guessing for fitPointDist ulp handling ((xValue - fitPointDist == xValue)  => try again with 2,3,.. time fitPointDist

../curvedLines.js
../flot/*

Fix compatibility with thresholds by epuidokas 

No more holes is the curve when there is not the amount of points in top and bottom curved line.

Flot is already doing it by itself

Prevent calculateCurvePoints from being called twice when filling & drawing line

- removed require.js stuff
- moved options from line: {} back to curvedLine: {}
- resolved a bug with the fit option
- updated examples

Define fill

Although fill was used to determine the fill of the curved lines, it wasn't defined.

Now let flot do the hard work. So all lines options are supported (date axis, shadow, gradient fill, ...)

Small bug fixes
- fill opacity always defaulted to 0
- check of Array.map

added saddle detection which should result in nicer curves and hopefully does not lead to new problems

however to detect the need of a conversion only the first entry in the data array is checked
and the conversion is not really efficient.