Investigate better layout for laptops or larger screens

[fuddster]

Display is optimized for phone/portrait layout. If a display supports it should we display all pages?

[zaaj]

Team 95, The Grasshoppers has been using a modified version of ScoutingPASS where we put all form fields on one tab, and just scroll for fields that don't show on the first screen. We do use section dividers for visual separation though.

Our scouting team is small enough each scout typically enters data for all three teams on an alliance, so we put three copies of the form on the screen, at first just with a frame set, holding three copies in side-by-side frames, resulting in three barcodes.

Scouts found the independently scrolling frames awkward, so we did more code changes to make three columns on the main page without a frameset, adding a column prefix to each elementID, and for loops to do form setup and getData tasks once per column prefix.

This results in one huge QR code at the end with three records in TSV format with Enter embedded between rows, so the scanner inputs directly into spreadsheet cells.

Haven't gotten my head around how to generalize the concept to make the number of columns be a configurable option though, so I haven't tried putting together a pull request for that type of change. Since this is an Investigation issue, I thought describing what we're doing might be a data point in your research.