-
Notifications
You must be signed in to change notification settings - Fork 1
Report week 6
This week, I reorganized the UI of the application and continued working on the camera activity.
Before working on the camera, I moved the content of the buttons to the real UI and then deleted the buttons. We now have the real UI combined with its features.
For my second task to differentiate between the mountains in the line of sight and the ones that are not, I used the existing LineOfSight and ElevationMap class to be able to differentiate between the mountains that are in the line of sight and the ones that are not in my line of sight. My estimates were completely off for this task. However, this was because the download of the elevation map was not yet downloaded in the background so I decided to also implement this not knowing that Ravi had a task assigned to himself for this.
For my last task, the estimates were too high and the implementation was much faster than I thought. I added the names and the height of the mountains in a text above the mountain markers.
I was able to complete all my tasks but invested more time than the 8 hours. Next time, I will double-check the scrum board before implementing something that is not completely in my task to not do the task of someone else. Besides that, the time estimates were much better this week. This is probably also due to the fact that I divided my tasks in multiple short tasks instead of having one big task.
This week I added the map to the empty map activity. For this used the osmdroid library. I added a marker for the user location and makers for all discovered peaks that the user has discovered. Two kinds of markers have been added, a black marker for all the peaks and a gold marker if the discovered peak is the highest mountain in the country. At activity startup, a bounding box enclosing all markers is created and zoom is made on that bounding box.
If the user clicks on a marker, the peaks informations are displayed in a custom info window (since the default one was too ugly)
If the user is not logged in, a toast is displayed at the bottom of the map. The map is in that situation still usable.
Adapt collection activity with real data.
Add some tests for the class.
I reached the two tasks within the planned 8 hours.
Next week i will work on settings activity
This week I finished the "friends system" of the app.
I created an activity showing the friends of the logged user (through a dynamic list), where you can press on each friend to see their score (but could be easily extended to show other things).
In addition, from the friend activity, you can also delete a friend.
The activities were quite easy to implement as the already implemented rankings and collected mountains work in a similar way.
The tasks took just a bit more than expected, meaning I'm finally getting better at estimations. I did not encounter any relevant problem.
In the next weeks, I will keep splitting my tasks into smaller ones because, from what I have experienced this week, it is much better to manage time this way.
This week I first connected the file path system (where photos taken with the app i saved) with the gallery. After that I did a bug fix regarding when textViews had too much text. My initial estimate was that the gallery connection would take the whole week (8 hrs) because of being able to implement tests when using the file system. However it was a lot easier then expected, so I finished the task too fast and needed to find a new task. We decided as a team to create a new column/card on the ScrumBoard that is called Bugs/fixes. Which contains problems that has appeared. So I could easily take a task from that list. What I learned this week is that it is better to try and split your work into several smaller tasks. That way it becomes easier to estimate and you won't get in trouble if it goes to fast or too slow.
I started this week working on the caching part of the app thinking that using android http cache system would work. It turned out that the API that we are using for the elevation map doesn't provide headers for caching. As we are changing a lot of things in the classes that require caching, I decided to alt these tasks and work on the downloading of offline content.
I implemented an activity that allows the user to enable offline mode by selecting a location on the map around which an elevation map and POIpoints would be downloaded and saved. The part to allows the user to select the point on the map took me a long time (8-9hours) as I had to learn about the Osmdroid API for displaying the map. The tests for that part are ready and working.
Then I proceeded with the downloading and saving part. As the classes that provide the data to save were modified during this week I had trouble implementing this part. I am thinking of splitting this task in subtasks as it is proving to be more difficult than I expected.
Our group this week was really efficient. Every member completed his tasks that were planned. That's a first!
We're also all getting better with the time estimates. We are at a point of the project where we have implemented a lot of features and probably will begin soon to update the existing features instead of adding new ones.
The code coverage is at 90% which was our initial goal. We will try our best to keep this value above 90%