raise more meaningful error if fx name isn't recognised
Don't use the term job, instead refer to the run button.
Store the specific time each job started
Always determine virtual run time wrt job local start time:

* previous behaviour, whilst it makes sense when multiple jobs are running
  and interacting, was potentially confusing in the current use-case of
  code, run, stop, code, run, stop...

* revisit this behaviour in version 3.0 when we make more of a focus on
  live coding
space out output pane for greater clarity
Don't clear output pane on stop, instead clear on run:

* User has a new preference toggle to stop clearing output on each run
* Allows behaviour to be studied in terms of the output - especially useful    
  now that timing information is available.
round current job time to 4 decimal places
Start work on attempting to get error messages from server available in Qt client:

* still more work here - doesn't seem to catch exceptions in the ruby process yet. If anyone has any suggestions - I'd love to hear them.