compose-jb

2078 Commits

244 Branches

378 Tags

388 MiB

Tree: cc0e18474a

Commit Graph

Author	SHA1	Message	Date
Alexey Tsvetkov	58b0a22fb5	Allow customizing Compose compiler plugin (#2347 ) By default, the Compose Multiplatform Gradle plugin uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>` as a compiler plugin . However, a new version of Kotlin might be incompatible with the default version of compiler plugin. Previously, that forced users to update to a new version of Compose Gradle plugin & Compose libraries in order to use a new version of Kotlin. Accordingly, Compose framework developers had to release a new version of all libraries, when a new version of Kotlin is released. Some time ago the Compose team at Google made it possible to update a compiler plugin without updating the Gradle plugin and/or all Compose libraries https://developer.android.com/jetpack/androidx/releases/compose-kotlin This change allows to specify a custom compiler artifact by using the following DSL: ``` compose { kotlinCompilerPlugin.set("<VERSION<") // or kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>") } ```	2 years ago
Igor Demin	b1d8682cbe	Automatically add `-Dcompose.application.configure.swing.globals=true to run/package tasks (#820 ) When users run/package application we will configure Compose to work as standalone application. It means we will override some global Swing properties in Compose initialization function: - sets system property `apple.laf.useScreenMenuBar` to true - sets system property `sun.java2d.uiScale`/`sun.java2d.uiScale.enabled` automatically on Linux - sets UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName()) When users don't use those tasks (when they use Compose in an existing Swing application, or in an IDEA plugin), this property will not be set, and so we will not override Swing globals.	3 years ago

Author

SHA1

Message

Date

Alexey Tsvetkov

58b0a22fb5

Allow customizing Compose compiler plugin (#2347 )

By default, the Compose Multiplatform Gradle plugin
uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>`
as a compiler plugin .
However, a new version of Kotlin might be incompatible with
the default version of compiler plugin. Previously, that forced
users to update to a new version of Compose Gradle plugin & Compose libraries
in order to use a new version of Kotlin. Accordingly, Compose framework developers
had to release a new version of all libraries, when a new version of Kotlin is released.

Some time ago the Compose team at Google made it possible to update a compiler plugin
without updating the Gradle plugin and/or all Compose libraries
https://developer.android.com/jetpack/androidx/releases/compose-kotlin

This change allows to specify a custom compiler artifact by using the following DSL:
```
compose {
    kotlinCompilerPlugin.set("<VERSION<")
    // or
    kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>")
}
```

2 years ago

Igor Demin

b1d8682cbe

Automatically add `-Dcompose.application.configure.swing.globals=true to run/package tasks (#820 )

When users run/package application we will configure Compose to work as standalone application.

It means we will override some global Swing properties in Compose initialization function:
- sets system property `apple.laf.useScreenMenuBar` to true
- sets system property `sun.java2d.uiScale`/`sun.java2d.uiScale.enabled` automatically on Linux
- sets UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName())

When users don't use those tasks (when they use Compose in an existing Swing application, or in an IDEA plugin),
this property will not be set, and so we will not override Swing globals.

3 years ago

2 Commits (cc0e18474a26dd839d36f6df13fdf5b6325e91dc)