Skip to content

Standup Meeting 3.30

KarlHan edited this page Apr 3, 2022 · 2 revisions

Standup Meeting Wednesday March 30

Attendance

  • jdumouch
  • ageolleg
  • tianming
  • burgosot
  • egwhite

What did we do

  • jdumouch. Look at javadoc generation error and QRCode/QRShot deletion issue.
  • ageolleg. Map progress on GitHub. Currently has a mapview that user can load and move around, and we can display QRShots on map.
  • tianming. Look at javadoc generation error. Fix android tests bugs and review code.
  • burgosot. Working on profile UI.
  • egwhite. Learning Espresso, starting android test on account fragment.

What will we do today

  • jdumouch. Fixing javadoc generation error.
  • ageolleg. Remove duplicate back button on map that's not functioning. Add zoom in/out feature and score/distance display.
  • tianming. Contact TA about javadoc issues.
  • burgosot. Profile UI to be improved to on Thursday (tomorrow)
  • egwhite. Account fragment android tests. Write more android tests after midterm is over.

Impediments in the way

  • Map requirement clarification, whether the map needs to display QRShot at any specified geolocation, or just ones that are close to player's current location (answered in elcass forum "project needs clarification" 7th question by the prof)

> 7)(US 05.0X.01)"As a player, I want to search for nearby QR codes by using geolocation." Does this mean putting in a location in a search field in a map and seeing the QR codes that are in the location and around it or is it that there is just a map with pins of the geolocations of QRs found and photographed?

A player should be able to find nearby QR codes. It can be implemented in different ways, but the idea is pretty simple: a player needs to somehow see the QR codes that are close to their current geolocation.

  • Javadoc was having compatibility issues with databindings, and Jayden was working on removing databinding library. (but later we discovered that navigation component also has some issues with javadoc, and after contact with TA we're keeping databindings for now)
  • Android tests are using mock objects, Espresso and ScenearioRules, which require some time to learn.

Clone this wiki locally