Project Weekly Logs

Note: Please answer the following questions:

• What have I done since the last Scrum meeting (yesterday)?
• What will I do before the next Scrum meeting (tomorrow)?
• What prevents me from performing my work as efficiently as possible?

Weekly Logs

1. Timothy Ngai

Week 12 (April 4)

• I made a demo of the game. My dart animation will begin when i click somewhere in the screen. It will leave a blood mark after the animation is done.
• I need to work on the back ground and image parts.
• I need to do some research on browsing image and using phone image as background.

Week 11 (March 27)

• I did not work on my assignment this week because I have to work on other assignment

Week 10 (March 20)

• I did set up a game loop. Now i am able to use simple X and Y to create animation. I am going to use this to make the dart animation.
• I need to research on getting the X and Y coordinate of screen touching or other method to control user input
• Since i need to do some research, It may take some time. I hope i can finish the game within the following week

Week 9 (March 13)

• I did some research and have some other game code using surfaceview, thread, sprite on gameloop and stuff. i am setting up the gaming environment now using surfaceview, thread and sprite.
• I need to finish setting up the game environment and ready to make a game out of it.
• Since this is the first time, I may get a lot of errors during this weeks works.

2. Joshua Byer

Week 13 (April 16)

• Last week I Completed the final report and did a presentation demo.
• We all out of time.
• I wasn't able to fix that bug, I tried.

Week 12 (April 6)

• Last week I made sure that the app worked well on a tablet in both landscape and portrait modes
• I will work on bugs and prepare for the presentation next week
• I do not currently have an android phone to finish the layouts for all devices.

Week 11 (March 27)

• I optimized the fragment usage so I don't have to constantly change fragments, GUI still needs work.
• If possible I well work on the GUI for both layout types and devices.
• I have 2 labs I have to work on for this course.

Week 10 (March 20)

• Last week I completed fragment usage along with complete base prototype for app.
• I intend to optimize fragment usage and increase GUI graphics, may include an instruction screen.
• Things are going along as expected.

Week 9 (March 13)

• Last week I completed prototypes for all pages along with file saving for meal entries.
• I intend to complete the design diagram along with finishing up the prototype?
• Things are going along as expected.

3. Wesley Hamilton - Rene Anderson

Week 10 (March 21)

• Successfully implemented the ContentResolver to locate Media files
• Temporary layout set for playlist
• Having trouble implementing the MediaPlayer service

Week 9 (March 13)

• Gotten some progress on the media player aspect of the application
• Need to look into the file-sharing aspect of the application
• Being delayed due to the amount of midterms and assignments lately

4. Norbert Curiciac

Week 13 (April 11)

• Due to the midterms and assignments we were not able to work more on the project

Week 12 (April 4)

• Due to the midterms and assignments we were not able to work more on the project

Week 11 (March 28)

In this week we completed 80% of our project.

Norbert

• Added the markers based on the new database.

Work needed to be done:

1. Location List Filters (complete, pending, incomplete)
2. Map Filters (complete, pending, incomplete)
3. Login Authenticate via API
4. Prepare DETAILS page (fix drop-down models)

Week 10 (March 21)

Norbert

• Created a temporary TreeMap object which stores Web Api data
• Loaded the Web Api JSON data to temporary TreeMap objects
• Created Temporary Map View, which displays the map
• Added Markers to the Map, which using the Web Api coordinates
• Created a Detailed View which displays more information about the current marker in case the marker was clicked ( InfoWindowClickListener() )
• We need to finish, final UI, local database and Views next week.

Week 9 (March 13)

• Gotten web service done and researched how to complete other functionalities such as Material Design
• Start developing the final UI next week
• Being delayed due to the midterms and assignments

5. Elsi Nushaj & Hyungryul Chun

Week 9 (March 13)

• Worked on the UI screens (Elsi) and setting up database integration (Steve) for the application.

• Continue working on the UI screen and start populating the database

• Problems running into database integration and the amount of course work from other classes

Week 10 (March 20)

• Developed more of the UI screens (Elsi) and database integration is now set up (Steve).

• We will try and finalize the UI for next week and get a good amount of database entries set up. We will also look into youtube integration and likely the random generator function.

• There is a lot of course work that is being piled on and it might be tough to keep up with the pre determined schedule. UI development is a little back tracked due to an assignment being due today, but Elsi will likely be back on track before the end of next week.

Week 11 (March 27)

• This week more UI work was done and is nearly entirely complete, aside from the BMI calculator screens. The timer visuals and function have been set up to receive the time from a user (Elsi). The random generator function was deferred to the following week as well as some of the DB entries. Facebook and youtube integration was researched a bit and some DB content was created (Steve).

• We have been a little back tracked due to a heavy course load from other courses and haven't been able to link up the DB aspect yet even though it is set up (Steve), but will be able to get back on track next week. Next week we plan on integrating the DB and trying to set up any of the two APIs (facebook and youtube).

• Similar to the other weeks the amount of course work and deadlines have made meeting the milestones a little more chaotic, but we are still getting work out and feel we are still on track. Other delays would likely be from the final projects remaining from other courses.

Week 12 (April 4)

• This week the Youtube aspect of the application was finished being researched and a miniature demo was set up in the weekly lab (Elsi & Steve). The demo will act as the basis of the Youtube integration shortly after this weekend. The DB was also hooked up to the application and will be populated this week in order to complete the random generator function (Steve).

• This week the facebook API will be looked at and possibly integrated. Database entries will be populated, the random generator function set up and the BMI calculator function and UI will be set up.

• There is a big written paper that is approaching the due date as well as some other projects, which might offset actual deadline dates. Based off the project pace we still look ok to meet the final deadline.

Week 13 (April 11)

• This week the Youtube integration was completed along with the BMI UI screen and the BMI calculator (Elsi). The facebook and random generator function are almost done being integrated (Steve).

• We are wrapping everything up and finalizing the last of the features mentioned above, also trying to add some more exercises to DB (Steve)

• This if the final week so it is a little hectic, but the application is pretty much done so we do not foresee any setbacks.

6. Nick Thomas

Week 9 (March 13)

• Did some research and discovered Android API for p2p communication (WifiP2pManager)
• Work on a barebones app that can discover and communicate (through text)
• I had some assignments and a midterm to study for this weekend(my main time to work)

Week 10 (March 20)

• Found a more suitable api Nsd manager, created a basic client server program.
• Test it on two devices, and incorporate a UI that allows users to select the device
• I needed another device and other assignments + work have taken more time time than expected.

Week 11 (March 27)

• Was not able to accomplish much work but did retrieve second phone to test on
• Test it on two devices and incorporate a better UI
• I was hampered by other courses

Week 11 (March 27)

• Created a very minimalistic selection view where users can select which device they want to connect to and chat
• Continue to develop the U.I to a more suitable set up
• Finding a way to differentiate between different types of incoming connections and my lack of knowledge in how to use NSD manager
• FYI cool video on NSD manager giving a how to: NSDManager

7. Petr Bouianov

Week 12 (April 4)

• OpenCV Implementation works, eyes located in picture functional
• Looking into hardware requirements for Android's Camera API Face Detection
• Looking into OpenCV Alternatives, will go with OpenCV if nothing promising found by end of week

Week 11 (March 27)

• Research on OpenCV implementation

Week 10 (March 20)

• Did not have much time to work on project
• Read over Material Design Guidelines
• Added bounds checking to camera zoom box

Week 9 (March 13)

• Progress on the Camera API part of the application. Started working on UI elements.
• Need to finish Camera implementation and start on facial recognition.
• Delayed due to midterms / projects / work.

8. Dylan Segna & Jacky Siu

Week 9 (March 13)

• Created some of the UI screens. Started working on dynamic UI creation at run-time. Setup the ViewPager for the UI screens using Fragments.
• Finish the rest of the UI screens and the dynamic UI creation. Setup the database.
• Issues sharing data between an Activity and it's Fragments. Possible resolutions: casting the Activity within the Fragment class OR make the data Parcelable (extra work).

Week 10 (March 20)

• Finished more UI screens. Possible implementation for data sharing between Fragments complete.
• Finish the rest of the UI screens and the dynamic UI creation. Setup the database.
• Some underlying design issues are causing slow progress.

9. Kelvin Ng & Eldon Lai

Week 12 (April 10)

• Removed the Geolocation services to simplify the app.
• We finished the app.
• We could not fix the problem with newly created blog entries that cause system error when being clicked on. The app needs to be manually restarted to allow access to newly created blog entries.

Week 12 (April 3)

• Implemented SQLite Database for data persistence.
• Test app and make improvements on UI design.
• SQLite Database operations work fine individually, but the overall performance is not reliable.

Week 11 (March 27)

• Implemented Google Maps and Geocoder functions to the app.
• Continue to research and work on web services, email, and social networking functions.
• Most of Android online articles and tutorials are based on Eclipse and we have to experiment with implementations on Android Studio.

Week 10 (March 20)

• Implemented app functions to record audio, take photos and capture videos.
• Integrate online services (location, navigation and weather services), email and social networking features.
• We did not encounter any major issues on our work in this week.

Week 9 (March 13)

• Created all UI pages and incorporated Recycler View and Card View of Material Design.
• Continue to refine UI pages and to integrate back-end multimedia support.
• We are not familiar with Material Design techniques and we need to do additional research on the related theories and code examples.

10. Jordan Wieb

Week 11 (March 27)

• The majority of the work was put into writing a full suite of functions and protections to ensure that sending and receiving data between devices functions smoothly and properly at all times, and proper support is given to the user in the event of an error.
• Test connections, finish units coding, implement all background game elements
• Assignments, assignments, assignments, and assignments.

Week 10 (March 20)

• Implemented code for user preferences, implemented the initial connection code, created basic classes for the game elements.
• Set up file reading and writing to store and retrieve units, create unit selection UI screens, finish connection code, create graphics process code.
• Need to complete an assignment for another class and spend time finishing up the BTS630 major project.

Week 9 (March 13)

• Researched various Android components, set up the front-end UI layouts and their basic interactions.
• Create the code for connecting users and the various back-end elements needed to set up the game (Units, grid, etc)
• Midterms, assignments with close due dates, most of which should be taken care of as of today however.

11. Luong Van Chuong

Week 13 (April 10)

• Finished
  • Nothing
• Upcoming Plans
  • Add Modify Quest
  • Add Notification
  • Finish up graphic animation UI
• Issues
  • Focusing on other course assignments.

Week 12 (April 3)

• Finished
  • SQLite Database
  • View Quest UI
  • Quest Content Provider
• Upcoming Plans
  • Drastically modify Android Project code for lab 6
• Issues
  • IDE having issues with Android projects and support files. Had to reinstalled Android SDK and Java SDK. The other causes were also the results of the file path of the android project location was too long.

Week 11 (March 27)

• Finished
  • Revamp UI
  • Added datepicker dialog
  • Added timepicker dialog
  • Design SQLite Database
• Upcoming Plans
  • Implement SQLite Database
• Issues
  • Modifying codes for reusability so that there can be multiple instance of the same picker in the same UI layout.

Week 10 (March 20)

• Nothing.
• Design and create SQLite Database.
• Got side-track.

Week 9 (March 13)

• First UI Done
• Design and create SQLite Database.
• Catching up on courses and mid-terms.

12. Sandeep Saldanha and Kris Vukasinovic

Week 13 (April 12)

• Make project Demo ready and ensure that all data is persistent throughout the Dashboard and Profile in order to use that information to decide score
• Study for Final Exam
• BTN415 Project Report

Week 12 (April 4)

• Endpoints for the transmitting data in our application that will help us to connect our application to our persistent data store. We also have the profile pages working properly on the application
• User authentication for the application while fixing up location data for the application
• BTI 420, BTS 430, BTN 415 and BTP 400 assignments for next week

Week 11 (March 22)

• Endpoints were completed on the back end part of things and Validation completed for the register page.
• We will have completed fixing up endpoints for the transmitting data in our application that will help us to connect our application to our persistent data store. We will also have the profile pages working properly on the application(Last weeks promise)
• BTS Assignment 3 due and BTP400 test 2.

Week 10 (March 22)

• Could not do anything due to alot of different assignments being due that week
• We will have completed fixing up endpoints for the transmitting data in our application that will help us to connect our application to our persistent data store. We will also have the profile pages working properly on the application(Last weeks promise)
• BTN 415 and BTS 430 tests for next week

Week 9 (March 15)

• We have completed the Google App Engine setup for our application while also finding a suitable resource to pull our Car data from. We are going to use fueleconomy.gov web services for our information as it gives us Greenhouse Gas Emissions for cars dating back all the way to 1986. The repository is extensive and the data they provide is sound.
• We will have completed fixing up endpoints for the transmitting data in our application that will help us to connect our application to our persistent data store. We will also have the profile pages working properly on the application
• Several project are due next week for BTC440, BTI420 and BTN415 but it should not slow us down by alot

13. Shianne Lee

Week 9 (March 15)

• Did some research to figure out the best way to handle my data.
• Complete the section that allows user to add their weight and retrieve the weight data, the UI for the section, and setting up the storage for all the data.
• Multiple tests.

Week 10 (April 2)

• Restarted the app because too many files were messed up.
• Re-do all the components that were previously done and get them working.

Week 11 (April 2)

• Nothing was done due to assignments.
• Start the food intake/calories section of the app.
• Assignments.

Week 12 (April 2)

• Creating the design for all the other pages and starting functionality for the "Add Food to List" page.
• Finish functionality and testing for food intake/calories section and start the goal setting functions.
• Assignments.

Week 13 (April 15)

• Finished design for all pages, got the database working and try to get information from it.
• Continue to try to get the information from database to display and complete the rest of the goals section.
• Study for exams.

14. Krishanthan Lingeswaran

Week 9 (March 13)

• Setup expandable list in a fragmemt and the navigation between other fragments. Implemented Navigation Drawer.
• Need to work on json requests to pull data from edmunds api.
• Tests.

Week 10 (March 20)

• Implemented Json Requests from API.
• Displayed the data from the JSON request.

Week 10 (March 27)

• Haven't had time to work on project much.
• Was reading up on various gallery implementaion. & Sliding tab layouts

Week 10 (April 3)

• Implemented sliding tab layout in app.

15. Andrew Li

Week 9 (March 13)

• Implemented navigation drawer UI, speak out text, add vocabulary to list
• To do before next scrum meeting: CRUD category, CRUD vocabulary, CRUD languages
• On track, no delays so far.

Week 10 (March 20)

• Added backend using greenDAO an ORM solution to persist objects and manage relations, updated UI mockups
• To do before next scrum meeting: CRUD category, CRUD vocabulary, CRUD languages
• Spent time researching backend solution thus did not have time to implement CRUD work

Week 11 (March 27)

• Implemented: CRUD vocabulary and phrase, persist multiple languages
• To do before next scrum meeting: CRUD category, CRUD languages
• On track.

Week 12 (April 3)

• Implemented: nothing
• To do before next scrum meeting: CRUD category, CRUD languages
• Worked on labs instead

Week 13 (April 10)

• Implemented: Static languages
• To do before next scrum meeting: CRUD category, select native language
• On track.

Week 14 (April 16)

• Implemented: select native language, dynamic fragment orientation/portrait views
• To do before next scrum meeting: nothing
• Complete

16. Tai & Yong

Week 9 (March 13)

• Implemented create ad functionality.
• Modified input text field to handle currency for pricing.
• Implemented create account and user signing in.
• Researching methods to implement image input.
• Need to research google map integration.

Week 10 (March 21)

• Let user input an image via image from camera or gallery.
• Persistent application data via caching objects in internal storage.
• Let user add location to ad posting with Google maps.

Week 11 (March 28)

• Validate a username and password
• Let users see a list of book ads
• Let users search books with titles

17. Albert Kim

Week 10 (March 21)

• Added search icon to action bar.
• Added an order by spinner for events.
• Added loading icon to activities.

Week 12 (April 4)

• Project is completed

18. Wai Kit Liew

Week 9 (March 13)

• Project Proposal
• Research location service
• Background process research

Week 10 (March 20)

• Project Design Report
• Start home page

Week 11 (March 27)

• Save location data to SQL
• Home page complete