adding intellij project files.
updated intellij project setup to match the project properties file.
started integration of the navigation drawer into the application.
updated icons for the activities.
added navigation drawer to Configuration activity.
switched configuration activity layout from FragmentTabHost to ViewPager; it's now possible to swipe from tab to tab.
removed Configuration, and Settings from the menu. they are accessible through the navigation drawer.
cleaned up, and fixed bug for the navigation drawer logic.
added navigation hubs for the configuration tabs.
updated navigation drawer expandable listview adapter to stores the expand/collapse state of the group(s).
fixed bug causing the ParametersTableFragment to crash on device rotation.
navigation drawer item selection bug fix.
updated google play services lib to the latest version (3136110 => 4030530).
updated ui to alter map padding when the navigation drawer opens/closes. This permits the map's controls to still be visible and reachable when the navigation drawer is opened.
refactored ui for the editor activity.
cleaned up menu interface/logic.
made more accessible option to keep menu drawer opened.
added bottom bar to hold the mission control buttons, and the mission status.
ui cleanup.
starting glass integration on the newui branch.
fixed ui issue with flight activity on landscape orientation.
intellij property files update.
updating google play service resources.
adding the original hud for glass support.
added previous version hud view for glass support.
added bluetooth server to relay mavlink packet from the android device to google glass.
completed integration of the mavlink bluetooth relay server.
This server allows devices that can establish a mavlink connection (via bluetooth, usb, etc...) the ability to share that mavlink connection via bluetooth with other devices (up to 7 in theory).
This can be used in scenario such as having google glass receive mavlink data from a device with a usb ground telemetry; or have one device act as an hub, while multiple (up to 7 in theory) 'viewers' share and view the mavlink data.
If the connected 'client' devices are also running DroidPlanner, they can also act as a hub while being connected to one, thus extending the reach of the original hub. And this can be repeated ad-infinitum (to be tested...).