0f5af82cb5
Build some convenienc functions for measurement entry fields
...
Move the weight field into text_entry
2024-01-31 09:16:35 -05:00
7ec48ded5d
Make the day summary use the view model
2024-01-20 17:04:20 -05:00
9bedb7a76c
Tons of linting and get tests running again
2024-01-20 15:04:46 -05:00
b5dcee3737
Update the historical view when a change happens in the db
2023-12-28 22:47:47 -05:00
0c3ae062c8
Save real data to the database. Load data on app start.
2023-12-28 22:46:44 -05:00
f422e233a1
Record data to the database
...
This isn't recording real data. It's basically discarding all
information from the weight edit field. But it is creating a record.
2023-12-28 22:43:56 -05:00
7a6e902fdd
Create placeholders in the historical view for days that are unpopulated.
2023-12-28 22:36:44 -05:00
6d9e2ea382
Switch to the updated emseries record type
2023-12-28 22:36:40 -05:00
04a48574d3
Develop a pattern to detect clicking outside of a focused child
...
Be able to respond to blur events and potentially be able to record weight.
2023-12-28 22:34:09 -05:00
383f809191
Open and style the day detail view and add it to the navigation stack
2023-12-28 22:31:07 -05:00
e30668ca8e
Drop DateTimeTz from fitnesstrax
2023-12-28 12:51:50 -05:00
af8f9b0244
Generate some random data and feed it into hte historical view
2023-12-24 19:13:49 -05:00
1b3ca7439d
Add styling to the day summary
2023-12-24 12:00:12 -05:00
3dc8be0d26
Render a weight record
2023-12-22 18:53:29 -05:00
43cd408e2c
Start elaborating upon the HistoricalView
...
I've created the DaySummary structure and set up a list view to go into
the historical view. One hard-coded date is visible as a placeholder to
start filling things into the day summary.
2023-12-22 17:32:45 -05:00
f19090311b
Extract all of the UI components into dedicated files
2023-12-22 15:17:22 -05:00
