Re: [rcpilot-devs] RCGS TODO

[Ian D. <occ...@ia...>]

Michael J. Pawlowsky wrote:
> Tracker View
>    - Distance Label
>    - Bearing Label
>    - Visual Alarm
>    - Zoom button background same color as video
> 
> Map View
>    - Have icon placed at proper position
> 
> User Preferences
>    - Fonts
>    - Protocol (NMEA , Amateur UAV Data Protocol)
>    - Altitude Alarm
>    - Individual Check Boxes per Alarm.
>    - Table Selection (which data to show or not)

I'd be happy to do all the Tracker, Map, and User Preferences stuff -- 
but I'll need a bit more detail about what all the bullet items mean.

Tracker View
----------------------------
Where do the labels go, and how do you want them to read? Can users turn 
them on and off? Do you have any examples from displays for life-sized 
planes?

What does the visual alarm look like? What sets off alarms?


Map View
----------------------------
Are we just placing an icon for the plan? What about the user's 
position? Should the icon be customizable? Should there be a label anywhere?


User Preferences
----------------------------

For fonts, do you just want a selector for small, medium, and large? 
What about the typeface, is there any reason to make that configurable? 
Why do people need to change fonts, anyway? Which fonts in the interface 
are affected by this? Would it make more sense just to give them a a 
point size selector? (ie, 10 pt., 12 pt, etc.) What happens if the font 
wouldn't fit in the existing layout, what steps should we take to warn 
the user or compensate?

Is the altitude alarm just a check box? Is there a test field to provide 
a specific height? How is the warning displayed to the user? Do we play 
a sound? If so, can they choose which sound? Will the warning be 
different depending on which screen they're looking at? If they're using 
VR glasses, pop up dialog boxes are pretty useless, right?

Which alarms have "Individual Check Boxes"? And how are all these alarms 
displayed when they go off?

Can you describe the table selection, and what should be configurable, 
in greater detail?

--ian