graph drawing..was way way easier than the canvas api.

that's a shame i suppose...was hoping i could use canvas.

this makes me rethink even using canvas at all for the kde plasma system
monitors, which this work was stemmed from...
quiet debug for now..so that i can hear my debug for Graph
tie in the graph to the client frame time

it now shows the smooth frametime instead of bogus values..
graph shouldn't take too much longer. i'll just set a min, max, and
a tooltip to show the value it's at.
Merge branch 'qtquick-attempt' into performance-graphs

sync qtquick-attempt with this
use Sample struct for graph..enables storing scaled values
client ms graph tooltip works and calculates properly..

should now scale with min/max as well (tooltip showed that the values of
the graph weren't being calculated properly)
add label to client frametime graph
fix tooltip using last mouse pos (should remedy a bit of delay)

add all grid lines (6 or so, evenly spaced), label them properly with
the numbers
tooltip looks a lot better now
almost have a new graph reporting server frametime

every tick of the client, it gets the value from the server
client and server perf graphs work beautifully, show tooltips, and current

frametime..now i should do similar stuff with the net
reimplement mouse press event for view, i'm sure we'll need it

though apparently the real fix is to use qml...sigh, i'm not very
good at qml and its input/focus handling..
Merge branch 'performance-graphs' into qtquick-attempt

Conflicts:
	src/globals.h
	src/server/server.h