Refactoring fragments 1 and 2 to match the new layout in fragments 3 and 4

License and Copyright Notice

By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).

Branch Name

issue_286_287_refactor1and2

Related Issues

Closes #286 (closed) and Closes #287 (closed)

During testing, discovered this solves the bug and closes issue #281 (closed)

Description

This request will update the XML file for fragments 1 and 2 of the Guest Registration form to match the new layout and design used in Fragments 3 and 4.

Steps to Test

1. Open the AVD
2. Navigate to the Guest Registration Form
3. Confirm that Fragment 1 and 2 have the same look and feel of Fragment 3 and 4

• Title and Fields are separated into sections with a white background
• Each section has the same padding
• Fields are 'full-width' to the ends of the screen
• Font is default font and centered on the title
• Each field has the same min-height
• The 'next' button is full-width.

Since this closes #281 (closed), confirm that you can 'tab' through the first fragment.

If looking at the XML:

• Layout should be a Linear Layout.
• A ScrollView should be within this main Linear Layout
• The ScrollView contains one direct child, another Linear Layout
• This inner-linear layout has the content of the form (fields, submit button)

Relevant Screenshots

Developer Notes

• With this layout, it's possible to move the 'Next' button out of the ScrollView. If we do this, it would be locked to the bottom of the screen. This might be a nice UI touch, but may also cause confusion if users don't know that they need to scroll to view more of a form. Can probably use coloring / enable/disable feature to make this more intuitive.