-
Notifications
You must be signed in to change notification settings - Fork 1
Report week 11
This week, I had 3 tasks. To save and retrieve the dates of the discovered mountains to/from the database, Add swipe gestures to navigate through the new UI and to update in general the UI.
The first task was quicker than expected. I did network a lot with the database before so I was not sure of the time it would take. The retrieving of the POIPoints was wrong on the first implementation but that was fixed quickly. The adding of the swipe gestures seemed also pretty straightforward at first but took longer than expected. The swipe gestures are not working on the SettingsActivity and are interfering with the touch listener on the MapActivity. Also, the swipe gestures are not as reactive as we would like. Basically, the swipe gestures simply open a new activity like on a button click. This can be changed by removing the activities and replacing them with a ViewPager with fragments. To do this late in the project is quite risky but I think it would be worth it. The last task also took longer than expected. To find the correct x and y position of the text to be drawn on the canvas took longer than expected.
I managed to finish all my tasks. Since the first tasks took me less time, I could focus more on the two other tasks.
This week I took two UI implementation tasks related to what I did last week: the challenges. I first implemented the challenges in the ProfileActivity by adding another ListViewAdapter. The currently logged user can see the challenges he is enrolled in by pressing the "challenge button" on the activity. A compact challenge item is displayed, with the photo of the founder, the remaining times, the points achieved. By Clicking on the item, the view gets bigger ad the podium of the challenge (3 users with most points gained). If a challenge is in pending state, a grayed out challenge item is created and it is displayed that the challenge is waiting for users to start. In my second task I implemented the same challenge list view in the social part of the app (i.e. for other users). That way the authenticated user can see other users challenges. I also added a join button when a challenge item is joinable (if the user is a friend of the logged user, if the user is not already enrolled in that challenge, if the challenge is not finished).
It took a bit more time than expected on the first task but manage to reduce the time I took for the second one (since I reused a lot of methods in the second task). In the coming week I'll work on bug fixes
This week I've been working on merging the new UI with the profile/social backend.
In particular, I worked on the new profile activity, which now is working also for non authenticated users. In addition, I completed the social activity by implementing the list of friends, in a similar way to the global rankings. I've also connected the social activity with the profile activity, meaning that by pressing on a social item you can see a user's profile.
Finally, I've been working on the DB offline mode and, in general, on improving the app behaviour when you want to interact with the DB with no connection (because the app was crashing in such situations).
I've spent a little more time than expected, as always, mainly because I underestimated the time to handle the problem of the offline mode for DB interaction.
However, I completed all my tasks, also because there is no much time left to complete the app.
This week I mostly finalized what I have been working on in bits these last couple of weeks. I actually added the new Ui we have created to the app so that it would be the main Ui. I also implemented so that a collected peak actually displays the correct country the mountain belongs to.
Since I had a clear idea on everything I was going to implement, estimating the time and doing the actual work was rather straight forward. I have learned how to do the "basic" Ui implementations which were handy in merging all Ui parts together in a way that is both scalable and easy to understand.
Because I had an understanding of how everything should be implemented I was also able to correctly estimate the amount of hours each task needed. Since this is the last week I would like to say thank you for a fun exciting course. It has been both thrilling and educative.
This week I worked on fixing the bugs I found last week on the LineOfSight method:
- I changed the way the line is drawn in the elevation map matrix. As I wasn't able to find anything online, I had to built it manually and that took way more time than expected, but now it's working except for a small bug
- The app now uses the settings to determine the range of the bounding box for all the features that require it (before, it was using fixed constants)
- I solved a small bug that caused some points not to be filtered correctly.
Despite splitting my tasks, I ended up working more than 16h, as fixing some bugs showed some other bugs I didn't know about. The bugs remaining seem to be minor bugs that should be easy to solve.
We managed again to finish and merge all tasks. We also added some last features. We are feeling the pressure of not having enough time to make the app work and look exactly how we want it to.
We must make the best out of it and now focus on the last details and bugs that exists in our app. We also want to participate in the battle of the app so we need to create the video which we haven't started yet until next week which will be also time-consuming.
To have a sixth group member would probably have been helping us to have more tie especially now at the end, where we want to release the best product possible and at the same time be competitive for the battle of the app.