James Cotton 11a08c186c AndroidGCS: Refactor the Fragments into their own package to keep the UI ...

"components" segregated.  Is this good practice though?  It means making a lot
of functions for the API between ObjectManagerActivity and Fragment public.

2012-08-08 13:14:38 -05:00

..

controller.xml

AndroidGCS: Controller gadget that uses virtual joypad to control UAV

2012-08-06 16:54:58 -05:00

dualjoystick.xml

AndroidGCS: Controller gadget that uses virtual joypad to control UAV

2012-08-06 16:54:58 -05:00

gcs_home.xml

AndroidGCS: Add a launcher icon for the SystemAlarms gadget

2012-08-06 16:55:01 -05:00

logger.xml

AndroidGCS: Logger now displays the number of bytes and objects logged.

2012-08-06 16:55:01 -05:00

map_layout.xml

AndroidGCS: Update the API key for my debugging key. I guess everyone testing

2012-08-06 16:55:00 -05:00

object_browser.xml

AndroidGCS: Add load button to the object browser.

2012-08-06 16:54:59 -05:00

object_editor.xml

AndroidGCS: Hardcode some dimensions on the editor dialog so the keyboard fits

2012-08-06 16:54:58 -05:00

object_view.xml

Added some missing files. Improved object browser to use ListView.

2012-08-06 16:54:53 -05:00

pfd.xml

AndroidGCS: Show some less shitty graphics for PFD

2012-08-08 12:20:29 -05:00

system_alarms_fragment.xml

AndroidGCS: Create a fragment API.

2012-08-08 08:37:35 -05:00

system_alarms.xml

AndroidGCS: Refactor the Fragments into their own package to keep the UI

2012-08-08 13:14:38 -05:00

telemetry_stats.xml

AndroidGCS: Add a telemetry monitor to the action bar that shows the TX/RX data

2012-08-06 16:55:02 -05:00

telemetry_widget.xml

Start of a widget for monitoring telemetry status

2012-08-06 16:54:52 -05:00