My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
Journal  
Record weekly progress
Updated May 27, 2013 by WebsterC...@gmail.com

Introduction

Each week you need to add a journal entry detailing:

  • The progress you made (once you start coding, mention the revisions for that week).
  • The problems you have encountered.
  • Lessons learned.
  • What you plan to do for the following week.


Details -- Yulia

4/13/2013 Done: Code refactoring, using a Delegate pattern, single issue user interface. To do: finish single issue displaying, improve navigation between activities.

3/26/2013 Done: The log in activity first functional test and the initial setup for user log in across application.

3/26/2013 Done: New Report form layout is ready. To do: start adding functionality to the form elements. Figure out how to record sound and take a picture. Design Login form.

3/25/2013 Done: Image downloading is implemented. To do: design Report an Issue form.

3/24/2013 Done: Both "Recent Issues" and "Followed Issues" buttons are functional now, still using mock data. Refactored Task and Activity classes for code reuse. To do: Implement image downloading. Think about Report Issue form design.

3/17/2013 Done: Initial code submission. To do: Do we want to use HttpURLConnection class? How to download images?

3/15/2013 For this week: learn how to send HTTP requests, parse JSON string responses, and display the results in a ListActivity.

3/7/2013 First project design is posted.

3/3/2013 Project and Wiki created.


Details -- David

5/18/2013: Java doc, and final code comment cleanup (didn't want to modify the code much during this week as it was the week before the final demo!) -- Thanks for such a good class Dr. Puder, it was honestly the best CS class I've had.

5/11/2013: finalized new report form, updated maps (initial zoom location/saved state/marker placement..etc) found out elusive bug-- NetworkLocationService is only loaded at boot and sometimes is killed by server (so geoloc wont always work if a lot of programs are/were open)

5/4/2013: UI update, and refactored the way that data was stored (note: Yulia did most of this, I just learned along side her that my previous methods were very spaghetti programming! thanks @ Yulia--this is a much cleaner way of doing it!)

4/27/2013: Finals/other project crunch time, so I wasn't so productive this week -- sorry!

4/20/2013: Lint/monkey features (Only brief introduction/background reading/tool tinkering was done.)

4/13/2013: code refactor (basically clean up my messy code, i.e. uniform coding practice instead of a spattering of this here and that there, Add comments, and a code "review" of sorts i.e. read shared code done by team mates with explanation for educational purposes

4/6/2013: more Google maps functionality: Drop a pin, ensure location is in America and other error checking, gather geolocation from pin dropped in a Latlng as well as street address and save that info to SD card--update: data is saved into internal app directory not SD card anymore

3/30/2013: Google maps: acquire a key (we actually accidentally acquired two keys due to communication issues--sorry about that Yulia, my fault!), sift through the Google map API instructions (we used v2) utilizes a fragment

3/23/2013: Media scanner and attempting to get a taken picture to be shown in gallery -- update: eventually abandoned because its not relevant for our functionality requirements.

3/16/2013: accessing the camera, microphone, and GPS (unrelated to the project, I also tinkered around with device orientation using gyroscope and accelerometer just for fun) and all that's involved in saving those two (audio codec's and .bmp processing..etc)

3/9/2013: App planning (functionality, code structure...etc.)

3/2/2013: learning SVN (never used it before) and eclipse and development environment

Powered by Google Project Hosting