From 7a60f4fdfbbc053f09c7a182fbc43367d4d62b98 Mon Sep 17 00:00:00 2001 From: BREW <81044362+b-re-w@users.noreply.github.com> Date: Mon, 26 Oct 2026 15:12:17 +0900 Subject: [PATCH] Chore: Bump the version to 0.0.4 --- CHANGELOG.md | 30 ++++++++++++++++++++++++++++++ Cargo.lock | 4 ++-- README.md | 2 +- compose-rust/Cargo.toml | 4 ++-- compose-rust/macros/Cargo.toml | 2 +- docs/guide/en/getting-started.html | 6 +++--- docs/guide/ko/getting-started.html | 6 +++--- docs/locales/README_ko.md | 2 +- 8 files changed, 43 insertions(+), 13 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b904eba0a..5e4dd6fd3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,35 @@ # Changelog +## v0.0.4 + +### Windows windows have caption buttons again + +The GraalVM Windows renderer, which is what ships, opened its window without configuring the +native chrome and composed the content without a caption or window actions, so minimise, +maximise and close were never drawn (#339). It now configures the window from the +application's `Chrome`, provides a 32 dp caption and the native window actions, and tracks the +maximised state. The window modules are pinned to a revision whose system chrome is on by +default and whose maximise button answers `HTMAXBUTTON`, so Snap Layouts open from it. + +### The mouse wheel scrolls the right way on Windows + +The Win32 window passed the wheel delta through unsigned, so content scrolled against the +wheel. The pinned window modules negate it into Compose's direction, and a script test checks +the sign. + +### Button and Chip labels stay on one line + +A parent that squeezed a Button or Chip measured its label at the width of one Hangul syllable, +so a label like 보내 broke over two lines. Labels are now one line with an ellipsis. A Button +still honours `max_lines` and `overflow` when the Host sets them (#328). + +### Releases and documentation + +The crates.io workflow installs every library the Linux renderer links and can be run by hand +for an existing tag. The documentation records that Windows ships the Kotlin/Native static +renderer only, and the SPEC adds centered sheets, full-size content under the title bar and +lists of shadows. + ## v0.0.3 ### The host can measure text, and text carries CSS properties diff --git a/Cargo.lock b/Cargo.lock index f7704d078..0138c74fa 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -32,7 +32,7 @@ dependencies = [ [[package]] name = "compose-rust" -version = "0.0.3" +version = "0.0.4" dependencies = [ "compose-rust-macros", "jni", @@ -40,7 +40,7 @@ dependencies = [ [[package]] name = "compose-rust-macros" -version = "0.0.3" +version = "0.0.4" dependencies = [ "proc-macro2", "quote", diff --git a/README.md b/README.md index 0b2c7c754..7763906b3 100644 --- a/README.md +++ b/README.md @@ -215,7 +215,7 @@ default, and `org.thisisthepy.compose.designsystem` for the contract both layers ### Using the crate ```bash -cargo add compose-rust@0.0.3 +cargo add compose-rust@0.0.4 ``` `cargo build` works out which renderer the target needs, downloads the release artifact for the diff --git a/compose-rust/Cargo.toml b/compose-rust/Cargo.toml index ca56e3966..6f1ee6842 100644 --- a/compose-rust/Cargo.toml +++ b/compose-rust/Cargo.toml @@ -3,7 +3,7 @@ name = "compose-rust" # 0.0.x on purpose: the boundary works and so do the desktop and iOS renderers, but the # widget vocabulary is still being filled in and nothing here is stable yet. A number that # says so is more honest than one that implies a first usable release. -version = "0.0.3" +version = "0.0.4" edition.workspace = true license.workspace = true rust-version.workspace = true @@ -55,7 +55,7 @@ native-renderer = [] # crate and not the other way round. `scripts/tests/core-has-no-dioxus.test.sh` fails the # build if that changes. [dependencies] -compose-rust-macros = { path = "macros", version = "0.0.3" } +compose-rust-macros = { path = "macros", version = "0.0.4" } # The Android shims are generated against jni-rs. Nothing here is linked into a desktop, # iOS or web build, and the alternative bindings generators were rejected for their diff --git a/compose-rust/macros/Cargo.toml b/compose-rust/macros/Cargo.toml index 0396cc427..928852481 100644 --- a/compose-rust/macros/Cargo.toml +++ b/compose-rust/macros/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "compose-rust-macros" -version = "0.0.3" +version = "0.0.4" edition.workspace = true license.workspace = true rust-version.workspace = true diff --git a/docs/guide/en/getting-started.html b/docs/guide/en/getting-started.html index e27660991..f78680111 100644 --- a/docs/guide/en/getting-started.html +++ b/docs/guide/en/getting-started.html @@ -78,13 +78,13 @@

Adding it to a project

shell
-
cargo add compose-rust@0.0.3
+
cargo add compose-rust@0.0.4
Cargo.toml, the line that command writes
[dependencies]
-compose-rust = "0.0.3"
+compose-rust = "0.0.4"

@@ -165,7 +165,7 @@

Your first application

- With compose-rust = "0.0.3" this program builds as it is. cargo run + With compose-rust = "0.0.4" this program builds as it is. cargo run downloads the renderer and opens the window.

diff --git a/docs/guide/ko/getting-started.html b/docs/guide/ko/getting-started.html index 4b583807c..3f6099b2c 100644 --- a/docs/guide/ko/getting-started.html +++ b/docs/guide/ko/getting-started.html @@ -77,13 +77,13 @@

프로젝트에 더하기

shell
-
cargo add compose-rust@0.0.3
+
cargo add compose-rust@0.0.4
Cargo.toml, 그 명령이 쓰는 줄
[dependencies]
-compose-rust = "0.0.3"
+compose-rust = "0.0.4"

@@ -163,7 +163,7 @@

첫 애플리케이션

- compose-rust = "0.0.3" 로는 이 프로그램이 그대로 빌드됩니다. cargo run + compose-rust = "0.0.4" 로는 이 프로그램이 그대로 빌드됩니다. cargo run 이 렌더러를 내려받고 창을 엽니다.

diff --git a/docs/locales/README_ko.md b/docs/locales/README_ko.md index c89e09538..f32d36894 100644 --- a/docs/locales/README_ko.md +++ b/docs/locales/README_ko.md @@ -201,7 +201,7 @@ Material 3, Apple HIG, Fluent, Liquid Glass를 비롯한 디자인 시스템 일 ### 크레이트 쓰기 ```bash -cargo add compose-rust@0.0.3 +cargo add compose-rust@0.0.4 ``` `cargo build`가 대상에 필요한 렌더러를 알아내고, 크레이트의 정확한 버전에 맞는 릴리스 아티팩트를