search

sanger96 / Happenings_Team-5_UTD_Senior_Design_Project

UTD Senior Design Project; Group Members: Gaurav Sanger, Jonathan Lam, Robert Dohm, Landin Kasti, Charles Eaton
3 stars 0 forks source link

[Front-end] Individual Event Page #108

Open jonathan-jlam opened 3 months ago

jonathan-jlam commented 3 months ago

This is the page that is navigated to from the event listing. I am working on this. Hope to get rough navigation set up by tonight/early tmrw morning so I can merge with FrontEnd.

jonathan-jlam commented 3 months ago

Event Individual Page is at the point where I think we could present it.

This is what it looks like right now.

image

IMPORTANT:

  1. You might need to drop your existing DB and let hibernate repopulate the data - see why below. I have also altered our backend quite a bit to accommodate functionality for the event page, so @rwdohm83 you might have to reload the server at some point (obv doesn't have to be anytime soon).
  2. I believe we are ditching the photo gallery idea, so I have re-purposed the photoSubDirectory field and associated column in the DB to hold the image for an event. 1a. The image is fetched straight from a static URL (hosted somewhere on UTD idk I got it from the pagescraper) 1b. Any NEW event created in-app will have a default image, go try and see.
  3. Back button to go back to the event list is added. This was necessary because we needed a way to go back from the event individual page after creating a new event.
  4. The RSVP button is semi-functional. We can probably leave it as is for presentation; can also fully implement functionality if we have time. The initial count for the RSVP is ACCURATE. So is the state of the button on page-load i.e. if the user is RSVPed for the event in the DB, the button will say "UN-RSVP" and vice-versa. Upon clicking the button, NO update is made to the DB, the only change is to the button text and RSVP count on the front-end side. Basically, the initial state of the button is always correct, but updates made in-app (by clicking on the button) will NOT be reflected in the DB.

General things:

  1. Event name at the top of the page will stick there upon scrolling.
  2. If there is no room number or no specific time frame for an event, the Views for them are deleted dynamically - just makes the formatting look nice. See below:

image

  1. I added some .png files to res/drawable that are the icons on the event page. If Android Studio complains about them being there, try re-syncing the Gradle files or closing and reopening Android Studio.

Things we could add (not high priority):

  1. Completing the functionality of the RSVP.
  2. In the little space next to the RSVP button, maybe show the club that is hosting event? For a UTD event we could just say so.