The goal of this first installment is to organize the code a bit so it's more readable,
clean up a bit of left over cruft, and manage link configurations (and links in general).

- Much simpler UI
- MVC style qml programming model

- Updated MainWindowTest to catch this problem
- Also implemented initial pass at SetupView unit test

- Updated MainWindowTest to catch this problem
- Also implemented initial pass at SetupView unit test

Controls respect QGCPalette settings. Also added test window.

- Central widget no longer stacked. Views are added/removed to layout
to switch view
- Dock Widgets are globals with single instance of each type
- Both central views and dock widgets are just-in-time created saving
lots of memory

- Central widget no longer stacked. Views are added/removed to layout
to switch view
- Dock Widgets are globals with single instance of each type
- Both central views and dock widgets are just-in-time created saving
lots of memory

Starting point for real implementation

Summary page is also the launching spot for the setup screens. No more
left hand set of buttons.

Needs to be re-written

Allows parameter access from QML among other things

The derived class wasn’t really adding any capabilties

Deployment target is still 10.6

Allows for UI unit tests to be written:
- Ability to respond to expected message boxes
- Ability to fail test if unexpected message boxes occurs

- allow unit tests to use QGCApplication
- clear global singletons for each unit test run

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