Interface Layout - CMPUT301F18T10/MediTrack GitHub Wiki

This is the login activity.

The user is sent here by default on launch
loginpage
A. Email input plaintext. The account logins use emails. Each account can be both a caretaker or a patient.
B. Password input plaintext. The user may have a password for his account, it is a typical password box with masked characters.
C. This button attempts to sign in using the info specified above. If successful, it will take the user to either his patients list or his problem list depending on whether they are logged in as a patient or caretaker.
D. This button pulls the above sign in info and creates a new account with the email and password. It then brings the user to the profile page activity where they are required to fill in remaining details before completing registration.

This is the edit profile activity.

The user is sent here when they press the edit profile button or register for an account
profileactivity
A. Plaintext of patient's username that the patient may edit, only viewable for caretaker
B. Plaintext of patient's real name that the patient may edit, only viewable for caretaker
C. Plaintext of patient's email that the patient may edit, only viewable for caretaker
D. Plaintext of patient's phone number that the patient may edit, only viewable for caretaker
E. Button to add a caretaker, opens a dialogue box to input a caretaker name. Only visible for patient.
F. Listview that shows current caretakers displays their titles and names. Clicking on a caretaker removes it.
G. Button to add a body cutout image, allows user to search through pictures saved on his phone and upload them to the app. Only visible for patient.
H. Listview of current body cutout images, shows the filename of the file uploaded. Clicking on a filename removes it.
I. Button to save the profile, will fail if any of the inputs are empty of invalid

This is the patients list activity for Caretakers.

patlist
A. The title is the name of the current logged in caretaker
B. The listview contains all the caretaker's current patients, displaying their names. Clicking on an patient name in the listview takes the user to the patient's list of problems
C. This button prompts the caretaker to enter a patient name to add to his list of patients.

This is the list of problems activity for patients and caretakers.

problst
A. The title is the patient's real name.
B. A listview which contains all the patient's current problems, using their problem title. Clicking on a problem in the list view will take the user to a problem activity containing the listed problem.
C. A delete button that is only visible for caretakers. Deletes this patient from his patient list and returns to previous activity.
D. The profile button that takes the user to this patient's profile/contact information.
E. The search button that takes the user to the search activity.
F. The add problem button that is only visible for patients. Creates a new problem and takes the user to a new view problem activity to view and edit that problem.

This is the view problem activity for patients and caretakers.

viewprb
A. The title of the problem. It can be edited by the patient but not the caretaker.
B. The comment for the problem. It can be edited by the patient but not the caretaker.
C. The listview contains records for the problem in each item, with subitem being the timestamp. Clicking on a patient record in the listview opens the view records activity with the details of that record. Clicking and holding on a caretaker comment in the listview deletes it.
D. The delete button removes this problem's data, including records, and removes it from the problems list. This button is hidden for caretakers.
E. When the patient clicks the floating add button, it takes the user to a new view record activity to edit the record. When a caretaker presses this button, they are prompted to enter a comment.

This is the view record activity for patients and caretakers.

viewrecord
A. The title of the record. It can not be edited.
B. The patient's comment for the record. It can not be edited.
C. The timestamp for when the record was created. It can not be edited.
D. An imageview for pictures added to the record. Clicking on the imageview loops the slideshow to the next image.
E. A button that takes the user to the body location map activity.
F. A button that takes the user to the maps activity.
G. A floating button that deletes the record.

This is the create record main activity for patients.

createrecord1
A. The title of the record which the patient can input.
B. The overall record comment which the patient can input.
C. A button that opens the file browser where the patient can choose pictures the add to the record.
D. A comment specific for the picture that the patient may input.
E. A button that saves the photo and attached comment, adding it to the record. After which, the patient may browse a new image and set a different comment to add.
F. This button takes the patient to the body map activity where they may add a body location to the record.
G. This button saves all the information of the record and creates it. After the record is created, it may not be edited.
H. Textview that displays the filename of the currently selected image.
I. This button takes the patient to a maps activity where they may select a geo location.

This is the body cutout activity for selecting a body location for records.

body
A. An imageview of the body cutout, loaded from whatever is provided in the user's account profile. Clicking on image will draw a red dot and save it's x,y coordinates. Up to two dots.
B. A text to label what parts of the body are marked. Used for sorting and searching.
C. This button saves the information and exits the activity.

This is the maps activity for selecting geolocations for records.

map1
A. Maps widget from google. The user will be able to specify a location on this map, and google api will be used to save the location and name of the location.
B. Saves the location of the map and exits the activity, returning to previous.

This is the search activity.

search
A. Text input where the user may enter a search keyword.
B. A group of radio buttons which specifies which category the searched keyword belongs in. Optional.
C. A listview of found problems containing the keyword specified. Clicking on an item takes the user to that problem page.
D. A button that commences the search function.
E. A listview of found records containing the keyword specified. Clicking on an item takes the user to that record page.