Removed the 2
Database data is actually added into the default database.
DB Stuff, continued

Adds object classes for Equipment, Muscle, Routine, and Workout data.
Routine can contain Workout, which can contain Exercises, which can contain Equipment.

A number of basic queries have been added. Will continue to expand on this.
Converting queries to use ArrayList<Object> (where Object is the appropriate class) instead of arrays.

NOTE: this is not yet fully complete.
DB Query Implementation Update

Added a ton of read functions to get data from the DB.

See "dbGetX" (where X is whatever you're trying to get)

Added a bunch of data object classes too. I believe that everything's captured at this point.
DB minor tweaks, code comments.

Bumped up DB id by one to account for a discrepancy in user_id in one of the tables. user_id is always an integer.
Changing Checklist Files
Merge remote-tracking branch 'origin/master' into develop
Populates list of exercises based on muscle selected
Also added a new query that selects exercises based on muscle_id
Fixed checklist order problems, beginning db loading
Merge branch 'master' of https://github.com/glp115/IST412
Merged Brian and Zach's changes, cleaned Wes's commit and pruned some non-essential class files. If you have any problems running the code with this commit, try this:

In Eclipse, go to "Project" menu, go to "Clean..." and make sure that the GymGuide project is cleaned.
Added Testing Repository Code

This testing code is UNtested. It's in a separate folder than the main code branch, however, so it should be fine!
Clara's MuscleExercise, WorkoutCreationArray, etc changes
Wes's Timer Pop-up update
DB Write Functions
Update README.md

added some coding guidelines and general information
Update README.md
Re-entered all pre-filled information regarding Sample Exercise 1. Went over the database structure and made sure all of the table structures are complete and correct.
Fixed the DatabaseAdapter to use try/catch blocks and adjusted the logic for going through all rows collected by cursor objects in order to properly store each row's data (before, only the first row of data was being saved appropriately as many times as there are rows). Apparently, sometimes cursor objects can return null (even when set up properly?), and the app will crash when these are encountered unless the try/catch blocks are in place. Currently, the "Load Workout" screen properly flips between the "Recent" and "All" workout tabs (as displayed on the UI group's powerpoint) and they are set up almost identically to the way the muscle selection page is set up. So far, the "All" tab displays a textView for each workout, but I am currently working on the dropdown menus. NYI: Querying the database for workouts completed within the past week.