Continue the scaffoldinf for the WP click creation. Now the waypoints are graphically shown in the MapControl. Ready to start interacting with the Waypoint widget

Cleaned up communication structure significantly, should now be easier to add new links. Signal bytesReceived(link, QByteArray) is now only way to pass on newly received data

Finished scaffolding the graphical addition of WP via the MapWidget. Added the possibility to display the latitude and longitude of the cursor as a property of QMapControl. Major reorganization of the MapWidget constructor

Major refactoring of the waypoint code. The new design fits the model-view-controller pattern better.

Added MAVLinkLight as an example how to add new protocols, it is currently not an actual implemented protocol

(cherry picked from commit c3194971)

fixed mutex usage in getTotalUpstream and getTotalDownstream and added initialization to connectionStartTime
(cherry picked from commit 15161eec)

fixed mutex usage in getTotalUpstream and getTotalDownstream and added initialization to connectionStartTime

(cherry picked from commit ed0fd7c1)

Made generator --pedantic GCC flag compatible/C89 compatible, fixed a bug where heartbeats where only sent to first link

Started to add support for autopilot firmware updates, added Linux compile instructions, fixed date in mavlink.h to english independent of OS language settings

Major cleanup of MainWindow constructor. All widgets have now the visible property set to false on its constructor

UASWaypointManager now implements the protocol described in http://qgroundcontrol.org/waypoint_protocol