djtai / beach-rendezvous Goto Github PK

Implement the "Movies" section. For now, there should be two: one for when the users want to CREATE a Movies event, and one for when the users want to FIND a Movies event.

NOTE: The main difference is the text displayed. Ideally, the UI should be the same.

Implement the "Sports" section. For now, there should be two: one for when the users want to CREATE a sports event, and one for when the users want to FIND a sports event.

NOTE: The main difference is the text displayed. Ideally, the UI should be the same.

Bug: When the user joins/creates an event, they are brought back to the home screen BUT are still allowed to press back - this shouldn't be.

Likely Issue: The MainMenu fragment is added to the backstack after joining/creating an event.

Possible Fix: Instead of adding MainMenu to the backstack, just pop the backstack until the user is at home.

After the user presses back enough, the app should close. Instead, they are brought back to the login activity - this should not happen. The following needs to be fixed:

• Store login access token after signing in*
• Check access token when app is opened

*Figure a way to access the auth token via Office 365 code (found in auth package)

Implement the "Food" section. For now, there should be two: one for when the users want to CREATE a food event, and one for when the users want to FIND a food event.

NOTE: The main difference is the text displayed. Ideally, the UI should be the same.

Bug: When a user tries to join a Movie event, the app crashes

Likely Issue: Since the code was somewhat copied from the Sports classes, it could be a variable issue, a NPE (null-pointer exception), or a Database issue.

Possible Fix: Data validation will help prevent NPE's; the FirebaseDatabase reference is created as final - this could be an issue, although I haven't tested it.

As wonderful as this application is, there is no custom launcher icon.

Let's design one.

The database for Sport events needs to be created and, eventually, linked to the "Search -> Sports" and "Create -> Sports" feature.

Ideally, the database will be created/managed using the Room Persistence library.

Issue: The red circle warning doesn't disappear after the user selects an appropriate date

How to replicate:

1. Go to "Create" section of the app
2. With the "Date:" box empty, click "Create" button so that the red circle warning appears next to date
3. Select a valid date (i.e., a date that is in the future). The red circle warning should still persists.

The following need to be addressed

MOST IMPORTANT

• Add ListView to home screen (via MainMenu fragment & it's relative .xml) to house the sports events the user has created. The layout of MainMenu should look similar to fragment_sportsevent.xml.
  NOTE: Just do the UI, @vooradi1993 will handle the logic.

LESS IMPORTANT

• Padding b/w arrow and edge of screen
• Change arrow icon to something simpler; make icon smaller
• Change green icons to a lighter shade of grey
• Test different fonts
• Add date picker next to Date text box // fixed with #42
• Add time picker next to Time text box // fixed with #42

When the screen is rotated, onCreate is recreated, essentially adding that creation to the fragment back stack.

Update the launcher icon, i.e., make it look up-to-date.

Also, the colors of the logo (seen on the login screen) do not match the colors found in the colors.xml.

NOTE: Not as important, but nonetheless should be considered if you have the time.

Currently, the bottom navigation bar displays the wrong information. The navigation bar should display, in order:

• Info
• My Profile
• Settings

This could, and might, change in the future. For now it will suffice for our "Dummy App" project.

1. Update info
2. Implement sections

It has come to my attention that the "Create" button should probably have a different name - maybe "Submit". Why? Well...when a user is in the "Create" section and they are about to create an event, the "Create" button is located directly above the "Create" nav bar button - do you see the problem?

It's not truly a problem - I just think it would make more sense.

When navigating via bottom navigation bar, it shows which fragment is currently open by making the icon bold.

The issue is when a user presses the back button on their phone - it doesn't update the icon, i.e., if you click Search, then click Create, and then hit the back button, even though you are back on the Search fragment, the Create icon is still bolded.

NOTE: I assigned this issue to everyone but only one of us needs to work on it really...I just thought I'd bring this to everyone's attention.

Further develop the search feature for the Sports fragment.

NOTE: The classes might need to be renamed so that our App's naming convention is the same.

The infrastructure is there, but the features have not been implemented yet. The overall task should be relatively simple:

• Fix the .xml files to look similar to their Sports counterparts
• Add the logic to each fragment, again mimicking their Sports counterparts

Since Sports is almost done, we can look to those files to see the similarities and differences.

If there is any confusion, please let it be known - we are all here to help each other, especially in these final days! Happy coding.

Issues:

• TimePicker doesn't properly show time selected, e.g., 11:01 appears as 11:1 (the first 0 never appears)
• Alignment of arrows (@SukhleenDhillon needs to push this code first)
• Make the Sports events not capitalized, e.g., Soccer instead of SOCCER

Application has no login activity. The login activity should ideally be implemented using Okta's API's - a secondary choice could be using students' BeachMail (i.e., Microsoft).

Further develop the create feature for the Sports fragment.

Create the main menu of our application, i.e., implement the "Create/Find Events" page.

The ListViews that show data pulled from Firebase aren't repopulated when the Fragments are popped off of the back stack.

I think I have a fix for this on one of the dev branches - I'll commit it, cherrypick it to the master, and test it out.

Bugs:

• Users shouldn't be allowed to select dates prior to the present date (this includes TIME)
• Events shouldn't be allowed to be created if the following fields are empty:
  • Date, Place, Time, Number of people, and Duration
• Duration should follow normal time constraints, i.e., users shouldn't be allowed to set a minute duration past 59 (e.g., 2:61)
• Users shouldn't be able to re-join an event they've already created (this could be solved by making the join button invisible if they've already joined it, or not displaying it, or something else)
• Check to see if someone has already joined an event

The "Home" section (accessed via the bottom navigation bar) should display two things:

1. Events joined
2. Events created

For now, placeholders will suffice, seeing as the database has yet to be implemented.

Enhancement: Some users have requested that they be allowed to name their events.

Possible Fix: Fixing the DB-related classes/entities, i.e., adding the parameters that allow naming events.

Using the strings.xml files that @jeremysellem has supplied, localize the app.

NOTE: Not as important. This issue can probably wait until the weekend, or even until next Monday/Tuesday (13th/14th).

Issue: When a user is in an EditText field they should be allowed to click-out of the box and have the keyboard disappear.

Possible Fix: I honestly am not sure.

The infrastructure is there, but the features have not been implemented yet. The overall task should be relatively simple:

• Fix the .xml files to look similar to their Sports counterparts
• Add the logic to each fragment, again mimicking their Sports counterparts

Since Sports is almost done, we can look to those files to see the similarities and differences.

If there is any confusion, please let it be known - we are all here to help each other, especially in these final days! Happy coding.