jacobrs / hwrkit Goto Github PK

The log in screen back end is all of the code which will ensure the user can log in and also the code which will determine whether the user will persist or not.

This logout tab will simply bring the user to the login page.

The logout tab will simply delete the user's information that we are currently storing. It will also bring the user back to the login screen after a successful logout.

The user is a teacher:
This stub view will let the teacher know that the statistics/averages are not available yet.
OR
We can hardcode some stuff.

The user is a student:
This stub view will either display hardcoded personal statistics.
OR
We can simply let the user know that their personal statistics aren't ready yet.

The main fragment will display information depending on whether the user is a teacher or student.

The user is a student:
The view will display averages (maybe) and statistics that relate to the specific user, they will also see the times they have inserted doing homework.

At the bottom of this page there will be a button which will allow them to insert a time period for which they have done homework, this can be done either manually (user picks two specific times), or we can use a timer (we store the times for when the timer starts and ends).

The user is a teacher:
The view will simply show statistics for their classes they are teaching. (This is the Statistics Tab for teachers)

The stub for our classes tab will have a list view of three hard coded classes. When pressed they will lead the user to the correct page (using our function stub that determines whether the user is a teacher or student)

Shared
ListVIew of classes (Hard coded for now)

Things on this page for students
When the user clicks a class lead them to a page with their time spent doing homework in this class or we can have a text field letting them know they haven't done homework yet, this will also have the button stub for adding a new time period.

Things on this page for teachers
When they click a class lead them to a view which has hard coded values or a text field saying averages and statistics aren't available yet.

The log in screen is the first activity that the user will encounter when opening our application, it should have a username and password field with an option to stay logged in and it should also have a button which will log them in.

NOT SURE YET:
There should also be an option which will lead the users to a register page.

The user is a teacher:
This tab will be used as an overview tab where they can view statistics for all of their classes. It is the teacher's main fragment view.

The user is a student:
This tab will be used to display personal statistics based off of information we have on the user (the time they've spent doing homework in correlation with their marks)

The prototype login view will be purely frontend, the login button should move the user to the main fragment.

Things on this page
-Two text fields allowing users to input a username and password
-Button which will lead them to the main fragment
NOT SURE YET:
-Some sort of way to let the user go to a register page

The Prototype for our main fragment should simply have a working menu drawer and should also have a button in the bottom right which is a stub for inserting new times. We can make a stub function for whether the user is a teacher or a student (this will be hard coded for now) and we will have to change what is displayed depending on the user's type.

Things on this page for students
-Button in the bottom right
-Text field letting the user know that they have not entered any times yet.
OR
-Hard coded times and statistics

Things on this page for teachers
-Text field letting them know that there are no statistics yet because no homework has been done
OR
-Hard coded averages and statistic

Shared:
The classes fragment will contain a ListView of all the available classes the user can view.

The user is a student:
If a student clicks a class the app will switch to a statistics view showing the student’s time spent and the homework blocks he/she inserted. Students will also have the round “add a homework time” button in the bottom right that shows up in the main fragment.

The user is a teacher:
Clicking a class will bring them to a view which will display average statistics it will also include a student ListView.