Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
4 changes: 2 additions & 2 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ default, and `org.thisisthepy.compose.designsystem` for the contract both layers
### Using the crate

```bash
cargo add [email protected].3
cargo add [email protected].4
```

`cargo build` works out which renderer the target needs, downloads the release artifact for the
Expand Down
4 changes: 2 additions & 2 deletions compose-rust/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion compose-rust/macros/Cargo.toml
Original file line number Diff line number Diff line change
@@ -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
Expand Down
6 changes: 3 additions & 3 deletions docs/guide/en/getting-started.html
Original file line number Diff line number Diff line change
Expand Up @@ -78,13 +78,13 @@ <h2 id="install">Adding it to a project</h2>

<figure class="codeblock" data-copy="Copy" data-copied="Copied">
<figcaption>shell</figcaption>
<pre><code>cargo add [email protected].3</code></pre>
<pre><code>cargo add [email protected].4</code></pre>
</figure>

<figure class="codeblock" data-copy="Copy" data-copied="Copied">
<figcaption>Cargo.toml, the line that command writes</figcaption>
<pre><code>[dependencies]
compose-rust = <span class="s">"0.0.3"</span></code></pre>
compose-rust = <span class="s">"0.0.4"</span></code></pre>
</figure>

<p>
Expand Down Expand Up @@ -165,7 +165,7 @@ <h2 id="app">Your first application</h2>
</figure>

<p>
With <code>compose-rust = "0.0.3"</code> this program builds as it is. <code>cargo run</code>
With <code>compose-rust = "0.0.4"</code> this program builds as it is. <code>cargo run</code>
downloads the renderer and opens the window.
</p>

Expand Down
6 changes: 3 additions & 3 deletions docs/guide/ko/getting-started.html
Original file line number Diff line number Diff line change
Expand Up @@ -77,13 +77,13 @@ <h2 id="install">프로젝트에 더하기</h2>

<figure class="codeblock" data-copy="복사" data-copied="복사됨">
<figcaption>shell</figcaption>
<pre><code>cargo add [email protected].3</code></pre>
<pre><code>cargo add [email protected].4</code></pre>
</figure>

<figure class="codeblock" data-copy="복사" data-copied="복사됨">
<figcaption>Cargo.toml, 그 명령이 쓰는 줄</figcaption>
<pre><code>[dependencies]
compose-rust = <span class="s">"0.0.3"</span></code></pre>
compose-rust = <span class="s">"0.0.4"</span></code></pre>
</figure>

<p>
Expand Down Expand Up @@ -163,7 +163,7 @@ <h2 id="app">첫 애플리케이션</h2>
</figure>

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

Expand Down
2 changes: 1 addition & 1 deletion docs/locales/README_ko.md
Original file line number Diff line number Diff line change
Expand Up @@ -201,7 +201,7 @@ Material 3, Apple HIG, Fluent, Liquid Glass를 비롯한 디자인 시스템 일
### 크레이트 쓰기

```bash
cargo add [email protected].3
cargo add [email protected].4
```

`cargo build`가 대상에 필요한 렌더러를 알아내고, 크레이트의 정확한 버전에 맞는 릴리스 아티팩트를
Expand Down
Loading