From c83bca9a9de29c155d519ccea2e8a8d07acc5bac Mon Sep 17 00:00:00 2001 From: Yves Fischer Date: Wed, 17 Apr 2013 00:13:33 +0200 Subject: leveldb --- .../public/lib/flot-0.7/examples/time.html | 71 ++++++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 datastore-leveldb/public/lib/flot-0.7/examples/time.html (limited to 'datastore-leveldb/public/lib/flot-0.7/examples/time.html') diff --git a/datastore-leveldb/public/lib/flot-0.7/examples/time.html b/datastore-leveldb/public/lib/flot-0.7/examples/time.html new file mode 100644 index 0000000..da62347 --- /dev/null +++ b/datastore-leveldb/public/lib/flot-0.7/examples/time.html @@ -0,0 +1,71 @@ + + + + + Flot Examples + + + + + + +

Flot Examples

+ +

Monthly mean atmospheric CO₂ in PPM at Mauna Loa, Hawaii (source: NOAA/ESRL).

+ +

If you tell Flot that an axis represents time, the data will + be interpreted as timestamps and the ticks adjusted and + formatted accordingly.

+ +

Zoom to: + +

+ +

The timestamps must be specified as Javascript timestamps, as + milliseconds since January 1, 1970 00:00. This is like Unix + timestamps, but in milliseconds instead of seconds (remember to + multiply with 1000!).

+ +

As an extra caveat, the timestamps are interpreted according to + UTC to avoid having the graph shift with each visitor's local + time zone. So you might have to add your local time zone offset + to the timestamps or simply pretend that the data was produced + in UTC instead of your local time zone.

+ + + + + -- cgit v1.2.1