Skip to main content

max / makeover-touch

0.4.0: take makeover-layout 0.8 Breaking for the structural reason a makeover-suite bump usually is rather than for anything that changed here. This crate re-exports makeover_layout::Priority and names Column and Arrangement in its own vocabulary table, so a consumer resolving layout 0.8 alongside this crate on 0.7 gets two incompatible copies and the re-export stops lining up. Nothing here changes. makeover-layout 0.8.0 adds a placeholder and select options to Field; this crate has no opinion about either, since it answers what a touch device gains and loses and neither is a capability. Left lagging, this is not theoretical: goingson resolved three copies of makeover-layout at once (0.6 through makeover-tui, 0.7 through this crate, 0.8 direct) the moment it repinned makeover-webview.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-05 19:05 UTC
Signed with PGP, not checked
Commit: d4b9a2a72ed151688061c63e5587b6ab8db5353d
Parent: 805bd88
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-touch"
3 - version = "0.3.0"
3 + version = "0.4.0"
4 4 edition = "2024"
5 5 description = "The adaptation layer of the make-family design system: which affordances exist at a given input class and window size class. Names what appears and disappears, never how much space it takes."
6 6 license = "MIT"
@@ -8,7 +8,7 @@
8 8
9 9 [dependencies]
10 10 makeover-geometry = "0.6"
11 - makeover-layout = "0.7"
11 + makeover-layout = "0.8"
12 12
13 13 [lints.rust]
14 14 unused = "warn"