This change needs testing : M114 is unbuffered, and thus might break lookahead
for Marlin and results in laggy jogging. We need to see how bad this is and
find some smart way to do it (like to send the M114 only when the user stopped
clicking everywhere, by using some timer callbacks).

This is a first step towards using gcoder.GCode as a storage for print-time
gcode. Now all we need is a "gcode line id => (layer id, in-layer line id)"
mapping to be able to do the indirection.

This should parse parentheses correctly and handle (valid) gcodes such as
G1X2Y3, while before we were assuming spaces between tokens (which is wrong as
per the G-Code spec). This should fix req #333 in a clean and systematic way.
This is also a component for #343 (Marlin M114 response is in the form ok C:
X11Y22Z33E44, which we can parse with the same expression).

Compute the max of all total lengths

The computed duration is no more pessimistic, for a few reasons.
- the main one is that it does not take retraction into account
- Z moves are not taken into account either
- arcs are not supported
- the acceleration code seems to estimate acceleration time correctly but is
  wrong for deceleration
So instead of telling the user this estimation is pessimistic, let's just tell
them this is an estimate.

I'm hunting unjustified try: except: blocks.

The icon was adapted from the 24x24 "Refresh" icon from Humanity Icon theme.

Okai, this may not make that much sense. However when removing the mainloop,
pronterface was segfaulting when Python was freeing everything. As a
workaround, explictely destroy the wx application, which will cleanly free
things in order, while Python might destroy wx things in a random order.

Conflicts:
	printrun/gviz.py

As far as I understand, a wxFrame needs a wxPanel child, but we shouldn't
reparent this wxPanel to some other container. As a consequence, I created an
initial wxPanel for the gwindow wxFrame and assigned it the previous sizer
(instead of using the gviz panel as the wxFrame's panel).
Not sure why it wasn't segfaulting on my other systems, though.

Not sure about that dropping of the self.gwindow.Destroy try block, we'll see

The gauges options is a CLI parameter as having it as an option would be
too painful to handle for now.
Argument parsing has been improved so that pronterface can add its own CLI
parameters in addition to pronsole's ones.

Should fix #348

This reverts commit 02ef52d7.
First step towards getting the gauges optionally back for #296.

This should fix the weird graph background for #359

One of the strings is to give a hint for wrong baudrates (#276)