Added a custom formatter to the threads xaxis

The threads graph used to show up the absolute time on the x-axis.
This was very messy and confusing.
Instead I changed it to show seconds relative to browser's time.

Fixes #53.
Removed the running parameter from cpu table.

The running parameter is meaning-less by itself.
I removed it from the cputable template.

fixes #31.
added basic pause/play methods to base graph box
Merge pull request #60 from dzautner/change-threads-x-axis

Added a custom formatter to the threads xaxis
Merge pull request #61 from dzautner/remove-cpu-running-param

Removed the running parameter from cpu table.
added pause play button
added tranlsation of play/pause click events to custom events
added general event listeners to graph box.
added pausing to Graph APIs
Added check to test if the graph is displayed

When the play event is dispatched, all of the graphs are calling their own play method.
In turn, this method calls the render method, which renders the graph without checking
if it is even displayed at the moment, causing al of the graphs to render over eachother when the
play button is pressed.
This was easily fixed by keeping the displaying state of the graph (should it be displayed?)
as a property for every graph - set to true post render, and to false on clean.
Added proper initalization of parent class to grahs

The graphs in the system all extend the base GraphBox, but they did not
call the constructor of the parent.
As the initalization of the event listeners for the play pause events
happens in the constructor, I have added a proper call to the parent constructor
for all of the classes extending GraphBox.
Added a global "globalPause" property

Many classes need to easily know what is the state of the system (paused or not).
For that I have added a global property dynamically set when the play/pause events are triggered.
added threadgraphtimeline to custom order in makefile:
added a null check to a possibly undefined var
Now only initialize threadsLayout once in threadsHandler

The threads handler used to initialize threadsLayout every time in renderds.
This caused the selected threads to reset every route change.
Merge pull request #62 from dzautner/global-pause-play

Global pause play
Fixed dissapearing Threads Timeline

The threads timeline was updated by an interval set in the constructor
of ThreadsLayout.

Because the ThreadLayout class is initialized once, the interval will only
initialize once.
This becomes a problem when the "clear" method is called on route change.
The interval will get cleared, but will not be re set when the threads route
is called again.

Moving the interval setting to the "render" method solved the issue.
Merge pull request #63 from dzautner/fix-dissappearing-threads-timeline

Fixed dissapearing Threads Timeline