1.6.10-dev1575

Support source set's hierarchy for compose resources (#4589)

Compose resources can be located in different KMP source sets in the
`composeResources` directory. For each resource an accessor will be
generated in the suitable kotlin source set.

1.6.2

Changes since 1.6.1

Features

Common

• Support Kotlin 2.0.0-RC1

Fixes

iOS, Desktop, Web

• Propagate composition locals to layers in the (re)composition phase
• Add transactions to FocusOwnerImpl takeFocus and releaseFocus to prevent crash when a window is re-shown
• Fix crash and allow selection in SelectionContainer to start when drag starts below the bounds of the visible text

iOS

• Fixed crash in TextField when a last symbol is a carriage return symbol

Dependencies

This version of Compose Multiplatform is based on the next Jetpack Compose libraries:

• Compiler 1.5.11
• Runtime 1.6.4
• UI 1.6.4
• Foundation 1.6.4
• Material 1.6.4
• Material3 1.2.1

1.6.10-dev1571

v1.6.10-dev1571

[gradle] Fix test data

1.6.10-dev1561

Make desktop preview task fully configuration cache compliant (#4410)

The issue was in a case where there wasn't a direct dependency on the
skiko artifact, the task would attempt to get one at task execution
time. This moves that to task configuration time.

1.6.10-dev1559

XML resource optimizations (#4559)

Users noticed if an app has big a `string.xml` file it affects the app
startup time:
https://github.com/JetBrains/compose-multiplatform/issues/4537

The problem is slow XML parsing.

Possible ways for optimization:
 1) inject text resources direct to the source code
 2) convert XMLs to an optimized format to read it faster

We selected the second way because texts injected to source code have
several problems:
 - strict limitations on text size
 - increase compilation and analysation time
 - affects a class loader and GC

> Note: android resources do the same and converts xml values to own
`resources.arsc` file

Things was done in the PR:
 1) added support any XML files in the `values` directory
2) **[BREAKING CHANGE]** added `Res.array` accessor for string-array
resources
3) in a final app there won't be original `values*/*.xml` files. There
will be converted `values*/*.cvr` files.
 4) generated code points on string resources as file -> offset+size
5) string resource cache is by item now (it was by the full xml file
before)
 6) implemented random access to read CVR files
7) tasks for syncing ios resources to a final app were seriously
refactored to support generated resources (CVR files)
 8) restriction for 3-party resources plugin were deleted
9) Gradle property `compose.resources.always.generate.accessors` was
deleted. It was for internal needs only.

Fixes https://github.com/JetBrains/compose-multiplatform/issues/4537

1.6.10-dev1557

Handle special characters for quantity strings (#4543)

A follow-up PR for #4519, which handles special characters for quantity
strings.

1.6.10-dev1551

Handle special characters for quantity strings (#4543)

A follow-up PR for #4519, which handles special characters for quantity
strings.

1.6.10-dev1549

v1.6.10-dev1549

[gradle] Update gradle and AGP in test runs. (#4542)

1.6.10-dev1523

[gradle] Use @InputFiles instead of @InputDirectory to avoid crash wh…

…en the dir doesn't exist

1.6.10-dev1520

[resources] Use first of preferred locales instead of a current on iO…

…S (#4507)

There is a bug on iOS:
```
NSLocale.currentLocale() -> 'en-US'
NSLocale.preferredLanguages().first().let { NSLocale(it as String) } -> 'ru'
```

An equal result was expected!
the first method was used in a non-compose code and another one in the
compose code.
The PR fixes behavior in a non-compose environment.