-
Notifications
You must be signed in to change notification settings - Fork 1
Report week 9
This week, I started to update the UI of the camera preview for our new UI. The picture button and the change displayed pois button were changed. The compass is now removed by default but can be displayed with a button that indicates the heading. A profile button was added to the camera preview from which the user can directly log in to his google mail account. This was made in a transparent activity s.t. on every other activity, this can simply be called like any other activity.
A bug was addressed where the permissions were requested in the init activity but the main menu activity was directly called which made the permission request to be overdrawn by the activity. This is now resolved. The init activity now checks for the permissions using the Dexter library and requests them if they are not granted before continuing to the next activity.
Last, the feature to collect discovered peaks was added. If the user now looks at them they are collected and saved to the database when exiting the camera.
The time estimates for the tasks were pretty good except for the update of the camera UI which took more time than expected because there was still uncertainty about how it should look and work.
This week I worked on the settings and on the caching. For the settings I added a binding between some settings and the backend part. The POI discovery range can now be changed. The caching can also be enable and disable. Some other settings will be implemented after the rework of the UI. I had no trouble implementing that and it went quite fast. I added the caching of the topography map, so if the user leaves the app and open it again from inside the same bounding box, the map won't be downloaded again. Instead the map is retrieved from the cache. This is a huge advantage because the map download takes some time to complete. I added tests inside the already created cache test file. It was really hard to get the tests passing (not the new ones but the old ones) after some intense debugging and some rework job on tests I made them pass. Next week I'll work on tests that have already been written refactor is needed on some of them after the late changes. I will also imrpove the challenge functionnality.
This week I implemented a class to represent other users (i.e. not the one authenticated) so we can use it in the social activity to show profiles of other users.
In addition, I modified the RankingsActivity decoupling the activity logic from the DB retrieval of the actual data to display.
Finally, I started working on the challenge user's story, by implementing a small and simple first type of challenge, that will be modified and extended in future.
I did not face any particular problem and I spent only a little more than expected (but I have still finished all my tasks).
This week I worked on implementing the UI prototype to the Android Studio and XML files. Since I had done previous similar work I though that I would be better at estimating the time. However I have realized that UI-work is hard to estimate. Because if you get stuck on some functionality it will take a long time to find the answer. Most google answers seem outdated. This week that unfortunately happened to me, twice. Therefore I over worked by quite a lot of hours. In the future I will split UI work to smaller tasks and do more mergers,to be able to estimate easier and for every step I don't know how to implement it I will add a few extra hours of estimation just in case.
This week I worked on 4 different small tasks:
- For the first one I implemented a method to draw a bounding box in the
OSMMap. Now, when the user selects a location to download, it will display the bounding box in which the offline content will be downloaded. - For the second task, I made the
CameraUIViewobserveComputePOIPoints(which now implements the Singleton pattern). This way, theCameraUIViewreceives live updates when the user moves. There was a bit of struggle with the tests but in the end, everything was solved. - For the third task I re-structured the GUI for the
SettingsMapActivity. It took way more time than I expected as I had problems withOSMDroidmaking my activity crash, but I managed to solve it (I am still unsure on what caused the problem). - For my fourth and final task I analyzed the code to see if it was possible to use the cache when downloading offline data, my conclusions are in the description of the issue.
Doing smaller tasks proved to be better because the problems I had were solved more quickly compared to the other sprints.
This week we started implementing the new UI, we improved the offline mode and the settings. We also managed to start the new challenge system. Some of us faced some problems with some old tests that now sometimes seem to fail, but the app keeps working fine and we will address these problems in the next week. Except for the tests, things went smoothly: we communicated a lot, we helped each other and we successfully ended all our tasks.