monorepo/fitnesstrax/app/Cargo.toml

[package]
name = "fitnesstrax"
version = "0.4.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
adw             = { version = "0.5", package = "libadwaita", features = [ "v1_4" ] }
async-channel   = { version = "2.1" }
async-trait     = { version = "0.1" }
chrono          = { version = "0.4" }
chrono-tz       = { version = "0.8" }
dimensioned     = { version = "0.8", features = [ "serde" ] }
emseries        = { path = "../../emseries" }
ft-core         = { path = "../core" }
gio             = { version = "0.18" }
glib            = { version = "0.18" }
gdk             = { version = "0.7", package = "gdk4" }
gtk             = { version = "0.7", package = "gtk4", features = [ "v4_10" ] }
thiserror       = { version = "1.0" }
tokio           = { version = "1.34", features = [ "full" ] }

[build-dependencies]
glib-build-tools = "0.18"
Set up the basic data structures of a new fitnesstrax app. 2023-11-13 13:52:10 +00:00			`[package]`
			`name = "fitnesstrax"`
Bump the fitnesstrax version to 0.4.0 2024-02-09 14:48:34 +00:00			`version = "0.4.0"`
Set up the basic data structures of a new fitnesstrax app. 2023-11-13 13:52:10 +00:00			`edition = "2021"`

			`# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html`

			`[dependencies]`
Update to adwaita 1.4, and add a navigation page stack 2023-12-25 06:09:31 +00:00			`adw = { version = "0.5", package = "libadwaita", features = [ "v1_4" ] }`
Mild cleanups 2023-12-22 20:16:03 +00:00			`async-channel = { version = "2.1" }`
Introduce the RecordProvider interface DayDetailViewModel needs testing. I've worked out an improved API, and a set of tests to go along with it, and those can be made more easily with a mockable RecordProvider. So, in addition to stubbing out a bunch of tests, I've also created RecordProvider, mocked it, and implemented it for App. 2024-02-01 15:12:35 +00:00			`async-trait = { version = "0.1" }`
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 22:32:45 +00:00			`chrono = { version = "0.4" }`
Generate some random data and feed it into hte historical view 2023-12-25 00:13:49 +00:00			`chrono-tz = { version = "0.8" }`
Render a weight record 2023-12-22 23:53:29 +00:00			`dimensioned = { version = "0.8", features = [ "serde" ] }`
Set up the main views for the window, as well as the redraw policy Whenever we change views, we need to call the redraw function. That function will handle dropping the old view and populating the new one. 2023-12-18 23:30:41 +00:00			`emseries = { path = "../../emseries" }`
Set up a development gsettings schema 2023-12-07 14:45:56 +00:00			`ft-core = { path = "../core" }`
Create a test that verifies that a series can be made for a TraxRecord 2023-12-07 04:32:56 +00:00			`gio = { version = "0.18" }`
			`glib = { version = "0.18" }`
Add buttons with icons to represent workouts 2024-01-25 14:03:55 +00:00			`gdk = { version = "0.7", package = "gdk4" }`
Elaborate upon and format the welcome dialog 2023-12-19 02:14:08 +00:00			`gtk = { version = "0.7", package = "gtk4", features = [ "v4_10" ] }`
Update the record in the detail view on save 2024-01-18 12:43:18 +00:00			`thiserror = { version = "1.0" }`
Create a test that verifies that a series can be made for a TraxRecord 2023-12-07 04:32:56 +00:00			`tokio = { version = "1.34", features = [ "full" ] }`

Set up the bare minimum of a GUI app, opening only a single window 2023-11-20 03:47:36 +00:00			`[build-dependencies]`
			`glib-build-tools = "0.18"`