This repository was archived by the owner on Nov 6, 2018. It is now read-only.
forked from peacecorps/peacetrack-android
-
Notifications
You must be signed in to change notification settings - Fork 18
GSoC 2014 Pooja Bansal
Janice Niemeir edited this page Jan 31, 2018
·
1 revision
I am a final year undergraduate pursuing M.Sc. (Tech) Information Systems from Birla Institute of Technology and Science-Pilani,Pilani Campus (India).
My interests include Algorithms, Machine Learning, Artificial Intelligence. I love dancing and like travelling a lot!
Github
Linkedin
Facebook
Gmail
PeaceTrack - Android Application I am working on PeaceTrack Android Application under Systers Peace Corps Mobile Team where I will be implementing new features to the already existing android application(with the name 'RealTrack'). PeaceTrack would be a new version of RealTrack which collects and stores the data by Peace Corps volunteers to be reported later as VRF.
My recent pushes could be found here
Documentation of PeaceTrack including workflow,challenges,design
To be added soon
- Read the documentation and requirements of the project.
- Took mentors' opinion on features suggested by me. Looked into the detail of the same.
- My initial timeline included both iOS(mainly) and android development. But since I am being asked to develop android only, modified and updated the timeline accordingly
- Setting up development environment - Eclipse and android sdk
- Read about ActionBarSherlock library as it was recently added in the project.
- Successfully built the whole application and tested in android phone by installing the USB drive for my mobile(as emulator was too slow)
- Many changes in the application than one in the google play.
- I had issues with libraries - ActionBarSherlock and GridLayout while building the application. Project explorer was not able to detect these libraries even though I had included the jar files.
- Yes, I have resolved them. I imported these libraries in eclipse as projects.Then defined these projects as libraries and included in realtrack project, but had many errors so spent a lot of time debugging those. Actual problem was - the names of projects must be particular names which were mentioned in the code.
- No, they don't exist anymore.
- No.
- I plan to get my hands on coding next week and adding a new feature of ability to record local meetings. I have shared my timeline on my profile as well. Also, I will discuss the changes done in the application than the one deployed in the Google play with my mentors. This timeline is subject to change depending on the requirements of the app.
- On Track.
- Earlier I was assuming that PeaceTrack would have same UI as RealTrack, so was heading in completely different direction. Thanks to Neeraj(my mentor) who cleared out that to me and also suggested to update my timeline considering this major shift in understanding.Read some tutorials about UI controls,graphics etc. (as I have not worked on building UI in android before).
- Interacted with Shelagh and my mentors regarding interface and also cleared some doubts regarding requirements of project.
- Made Podio Account , so it would be easier for the team to interact and communicate.
- N/A
- N/A
- N/A.
- N/A
- I have a meeting with my whole team and PeaceCorps this tuesday regarding requirements of project.
- I have meeting with my mentors this Saturday (in IST) for code review and we will finalise our UI.
- I intend to complete user interface for android this week including the edits which would be discussed in Tuesday's meeting.
- I am little behind as I had something different in mind, but now I have corrected my timeline and would try to cover up this week.
- Had a meeting with PeaceCorps about the requirements of project. It cleared many doubts regarding what some terms mean such as outcomes,goals ; how Peacetrack is different from realtrack and how will it measure the progress of an activity.
- Worked on user interface and collaborated with Shelagh, discussed features of UI from user perspective.
- Did some coding for user interface and also wrote java classes for event handlers.
- Presented the demo of work done till now with team.
- N/A
- N/A
- N/A.
- Yes, Still there are questions about some functionality,requirement and also the UI which PeaceCops team could answer.(Discussed the same in our demo meeting with team)
- I will fix the bug regarding clickhander(still exists in my code).
- I will complete the event handlers for other pages.
- I also plan to work with Shelagh so that we can make our UI look alike
- will decide where to put buttons,clickable text and would make it more user friendly.
- As far as my progress is concerned, I covered the backlog of last week and done pretty much coding this week. Some doubts are not cleared( which PeaceCorps team would be able to clarify), other than that I am pretty much on track.
- Functionality questions were cleared in a meeting with PeaceCorps and a list would be uploaded on git specifying the priority of functions/features, so that we could focus on functionality with more priority first.
- Fixed the bug with the clickhandler of welcome page that was there last week.
- Worked on the event handlers of other pages as well.
- Pushed the code to git hub
- Tried fixing up the searchview bug, went through many stackoverflow answers; but could not fix it.
- I had a problem regarding searchview dialog box.I was implementing the seachview to give an search icon on the action bar, but whenever I was getting NullPointerException on .getActionView() of searchview. Then I tried using ActionBarCombat, but searchview was still null.I knew I was missing an easy step, so googled it for hours; read about menus,searchview to see if I was missing any point, but could not find it.
- No.
- N/A.
- N/A
- I will fix the bug regarding searchview.
- I will implement the login page functionality making sure that it appears only once when user downloads the app.
- Start writing classes for cohort management, and will read about the graph implementation for cohort profile.
- I am lacking behind on some things because of unforeseen issues and also I was travelling this week. I will try to cope up with these and get back on track
- Synchronized work with Shelagh
- Presented demo of current work in code review meeting, keeping iOS UI side-bu-side of Android's.
- Pushed current code on github for review
- Communicated with Vaibhavi (from info hub working on data design for PCT app).
- Read about implenting SQLite in Android.
- We planned to make some changes in UI, somewhat different from the one uploaded by Anna on github. We will forward our questions to Patrick from Peace Corps.
- N/A
- N/A
- N/A.
- N/A
- It was decided in the meeting that focus of the application should be on outcomes instead of activities and hence the UI needs to be changed. Also the users should be able to filter activities by outcomes or cohorts etc, will discuss with Shelagh how to do the design and navigation for this.
- Raj has suggested some changes in the code, so will do those and push the new code to github.
- Shelagh has shared a doc of questions to be forwarded to PeaceCorps. Will add the questions that were discussed in the meeting to the doc.
- Will be creating local database using SQLite.
- I had planned to complete UI before , still need to implement more changes. But as it seems, it is better to give time on UI and making it more user friendly by understanding more and more about the features. This would greatly help in the next goal of this application.
- Updated the screenshots of UI with the ones discussed with PeaceTrack.
- Added our queries(most of them were about UI) to the google doc to be sent to PeaceCorps.
- Discussed these queries in code review meeting and decided to review the timeline and complete one feature at a time(we will soon be getting feature matrix from PeaceCorps).
- Synchronized with Vaibhavi from info hub team(will be doing that this week as well).
- N/A
- N/A
- N/A.
- N/A
- Submit code with PR to systers github project.
- Complete Login functionality and collaborate with Vaibhavi on the same as she has completed some work on the Info hub for login.
- Write a list of positive and negative test cases and post the same on podio.
- Have a meeting with PeaceCorps this wednesday, will clear more doubts on activities and measurements.
- In the last code review meeting we decided to review our timeline as the design part took more time than expected because we were having a lot of doubts regarding the workflow.We decided to take simple approach and complete one functionality at a time(about which has been covered above).From now on we will be having a weekly meeting with PeaceCorps as well for better understanding of workflow and we will try to keep the questions/queries of each functionality documented.
- Worked on login functionality
- Username - check whether it has been entered else pop up a message saying "Please enter username"
- E-Mail Id - check whether it is in email format else pop up a message saying "Enter a valid email-id"
- Post - Drop down menu for 'distinct' posts selected from the database(this we will get from info hub)
- Sector - Drop a list of sectors for the chosen post(will get from info hub)
- Collaborated with Vaibhavi as she has started work on login from her end. Still need to discuss the API that she will be exposing to us to retrieve the data.
- Wrote positive and negative test cases for the login function.
- I had some bug in my code related to using the data from sqlite file and load the data into the system.
- They have not been resolved yet.
- Yes the issue still exists . I looked into the bug and looked for the same over internet but could not solve it.
- Yes I would look further into this again (could be the case that I am missing something here), if I am still not able to find it I'll take help of my mentors.
- I have submitted code for review, will implement the suggestions once it has been reviewed this week.
- Will discuss further with Vaibhavi on API and will implement the same
- have to read more about json objects.
- Research about how to automate test cases, Chiu - Ki has shared a link with me, will go through it.
- Remove the data table bug, have to look more into it.
- We have revised our timeline after mid-term and I am on track.
- Implemented the changes suggested by my mentor after code review.
- Had a meeting with peacecorps this week about outputs,outcomes,disaggregation buckets etc.
- Fixed the bug for fetching data from database,issue was -
- Code was checking whether there is a database at the path or not, it was not going to the statement where this database is copied to the system.So there was NullPointerException every time I debugged it, but could not find this until many days.
- Tested the code on my android device and gave a demo of the working code in weekly meeting.
- Read about JSON objects and automated testing in android.
- N/A
- N/A
- N/A
- My current module is having a dependency on info hub. As soon as info hub team team has prepared the API for peacetrack team(data fetching from their database) and it is up and running, I will be able to pull the data from there as well.
- Vaibhavi has been very coordinating all this time and has prepared the API for us. She will be able to prepare the documentation for the same by the end of the day and I will get started on data fetching(will keep her in loop of my progress as well).
- Go through Vaibhavi's work related to peacetrack. She has shared some links with me
- Write JSON Deserializer for deserializing i.e. extracting meaningful information from JSON strings. Java provides API which supports JSON Deserialization but I have to implement the function myself.
- Fill indicators table in local database with these fields as it might be useful later in the application as well.
- Test the first login page(Add Account page) whether it is being able to take post and sector fields.
- Serialize and give the first page information back to info hub.
- Get started on cohort functionality - will sync with Shelagh for this module as there had been a discussion about the fields while adding a cohort in peacecorps meeting this week.
- Create a pull request. I need to merge two repositories for this
- Read more about automated checking
- I knew of only log files to see the result of my test cases, Rose and Neeraj mentioned of using travis ,will read about this and how it can be used in android framework.
- Check out systers portal on how do they use travis
- I am on track.
- Had meeting with PeaceCorps , finalized about cohorts having two fields and many other questions were cleared up
- Weekly meeting with Malaria team where Shruti and Aneke presented their applications,discussed sync up of our UIs and we saw there were some similarities in our projects as well(such as graphs)
- Went through Vaibhavi's work and also her documentation of the project(authentication etc).
- My laptop crashed last week, so shifted my entire work(installing the development environment again etc) to another laptop.
- N/A
- N/A
- N/A
- N/A
- I could not start cohort functionality earlier as I was not sure what would be expected from info hub as I will be syncing up my data(writing JSON serializer) to push my data to the info hub. I am working on it now.
- Vaibhavi has prepared a documentation for us to understand the peacetrack API, would go through it.
- I am on track.
- Changed UI of Cohorts Add screen as discussed in previous meetings.
- Implemented adding cohorts functionality
- User can add as many cohorts he wants and if he tries to add the same cohort again, he would get a popup message asking him to change the name of cohort.
- Once user clicks on Save button, the information is saved in local database and user is re-directed to a page which lists all the cohorts present in local database.
- Completed delete and update method, but has to work on connecting it to UI.
- Finally was successful in creating a pull request(having difficulty in merging two repositories) and got +1 from mentor.
- Checked in the latest code till cohorts add and view all cohorts screen to github
- N/A
- N/A
- N/A
- N/A
- I will complete these features for My Cohorts -
- Delete - Thinking of having a long-press(keep any cohort pressed for 2-3 seconds), and it will show a delete button. Pressing delete button would again show a message asking user if he really wants to delete the cohort from local database.
- Update - Long press a cohort will show a modify button and clicking on that button will show the already filled in details in editable mode.
- Search - I already have search icon in action bar at the top, will add functionality to it.
- Need to further discuss about the long press feature with Shelagh - whether it is possible in iOS or not.
- Keep interacting with Vaibhavi for updates on infohub module.
- Get new changes code reviewed.
- Work on documentation of functionalities implemented so far.
- I am on track.
- Modified delete and edit options - overriding the new action bar (containing delete and edit icons) with the existing action bar when any row item is long pressed.
- Faced a bug in identifying the position of row selected(it took -1 as default value), whereas on manually entering the position value in debugger, it was working perfectly fine.
- Pushed my code to different branch
- Neeraj has solved this issue but I have not tried it on my machine - will compile and run it and then will create another PR.
- Started documenting the application. Includes
- Front end
- Back end
- WorkFlow
- Status of work done on both platforms
- Difference between android and iOS
- Issue of not being able to detect position of selected row.
- Yes, Neeraj has solved the issue.
- No
- No
- Complete the code modules for cohorts.
- Document the workflow and challenges of applications on both the platforms.
- Get started on synchronizing the data with info hub .Vaibhavi requires some additional permission to host the service - once it gets completed, I can start on the functionality.
- I am on track.
- Implemented search option at the top of screen(in cohorts).
- Completed edit and delete options
- User can delete more than one cohorts at a time. When user long presses on any row, a context action bar would appear having two options of edit and delete. If user now presses more than one, edit option would be hidden.
- In edit option first I store the old cohort name. Then I check (on pressing submit button) if this cohort name already exists(other than the old cohort name in database) so that we do not end up having two cohorts having the same name.
- Modified documentation - prepared a UI design flow chart (will continue to edit it)
- None
- N/A
- No
- No
- Code clean up and adding comments in the code wherever possible.
- Add a message alert before deleting any cohort.
- Continue documentation.
- I am on track.