mark-vasquez / fitness-log

Fitness-Log

fitness-log's Issues

Create the Room Database API

• program table
• workout_template table
• exercise_template table
• set_template table
• workout_template_exercise table
• workout_session table
• workout_session_exercise table
• workout_session_exercise_set table
• ProgramDao
• WorkoutDao
• ExerciseDao
• SetDao
• HistoryDao

Implement Basic UI for ProgramFragment and ProgramEditFragment

Description:
Introduce basic functionality to ProgramFragment with a list of dummy placeholder programs and corresponding edit buttons as well as a "Create Program" button. Both buttons lead to a ProgramEditFragment that contain either pre-populated fields for editable program data or an empty fields to create a new program

Todo:

ProgramFragment:

• Implement a RecyclerView grid for the list of programs
• Add a "Edit ${programName}" button that will navigate the user to the ProgramEditFragment with fields pre-filled from the selected programName
• Add a "Create New Program" button that will navigate the user to the ProgramEditFragment with empty fields to create a new program

ProgramEditFragment:

• Fragment should have fields that are either blank when "Create New Program" is clicked or pre-populated with passed in data from the ProgramFragment when "Edit ${programName}" is clicked
• Fields should contain: Program Name label with EditText, Schedule label with CompoundButtons to toggle each day of week, and Workouts label with list of workout_templates associated with the Program
• Add a "Add Workout" button to add to list of associated workouts. (No need to implement yet)
• Add a "Cancel" button to cancel the creation or edit of the associated program. Should Navigate back to ProgramFragment
• Add a "Save" button to save the changed input fields to the database. (No need to implement yet until Workout feature is finished)

Note:

• Room database will be implemented with the ProgramEditFragment's "Save" button after this UI is built out.
• No fancy styling needed yet, just get the button functionality and navigation completed

Implement Homepage Activity with Bottom Navigation

Description:
Set up the main homepage activity for the app. This activity should feature a bottom navigation bar that allows users to switch between three primary fragments.

Fragments to Implement:

• History Fragment: This fragment will display the user's workout history.
• Workout Fragment: Here, users can view and engage with their current workouts.
• Program Fragment: This section is dedicated to overall workout programs and schedules.

Acceptance Criteria:

• A bottom navigation bar is visible on the homepage activity.
• Tapping on a navigation item switches to the respective fragment.
• Each fragment should have a basic layout or placeholder content for now.

Connect Repository and ViewModel to DAOs

Setup domain layer and repositories