This mechanism automatically queues data into the correct thread where necessary, otherwise the method is invoked directly with low overhead.

At the same time remove the UDP socket event workaround. It is not a problem.

This way we don't need macro-magic to deal with
different operating systems and compilers.
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

There are many ways of iterating over lists in C++/Qt.
In the specific case of QStrings, it is known [1] that using
foreach with const references avoids the creation of new
QString objects in each iteration, reducing the time consumed
by the loops.

[1] https://blog.qt.io/blog/2009/01/23/iterating-efficiently/Signed-off-by: Anselmo L. S. Melo <anselmo.melo@intel.com>

Instead us a Toolbox concept which hangs off of QGCApplication

- Delete all old map code

Also:
- Remove unused code

- All resources are either under src or under resources dirs
- Removed files top level directory
- Move flightgear files to top level dir

Moving methods from MainWindow to QGCApplication so that more things
can run without a window. Helpful for testing.

Subclass of QMessageBox which re-implements the static public
functions. There are two reasons for this:
1) The QMessageBox implementation on OSX does now show the title
string. This leads to message boxes which don't make much sense. So on
OSX we set title to text and text to informative text.
2) If parent is NULL, we set parent to MainWindow::instance. This
prevents message boxes which can go behind MainWindow

Using QFileDialog directly on OS X can hang intermittently due to Qt
bug.