v1.0.0-alpha10-118

[sellmair]

Call for Feedback

This build switches Hot Reload from using 'continuous builds' to the 'explicit reload' model.
Previously, anytime source code changed and was saved to disk, a daemon would have picked this up, recompiled the cod,e and sent a 'reload' request to the application. With the 'explicit reload' model, reloading requires explicit consent from the user.

Note: CLI

CLI usage:
Starting the application (unchanged)
kmp: ./gradlew jvmRunHot --mainClass myMain
jvm: `./gradlew runHot --mainClass my.Main

Requesting a recompile & reload
./gradlew reload

The continuous mode can be re-enabled on CLI using the --autoReload or --auto option
(e.g. ./gradlew jvmRunHot --mainClass {{ my class }} --auto)

Note: IDE

When Hot Reload is launched from the IDE, the continuous mode is still enabled.
Later implementations of an IDE plugin will take care of explicitly requesting reloads.

Other Changes

• Fixes in devtools: Window management, fixed reload animation
• Fixed deadlock in orchestration
• Always show reload counter in devtools (even when minimized)

Plugin

id("org.jetbrains.compose.hot-reload") version "1.0.0-alpha10-118"

Note: The 'dev' builds require the firework repository:

pluginManagement {
    repositories {
        maven("https://packages.jetbrains.team/maven/p/firework/dev")
    }
}

dependencyResolutionManagement {
    repositories {
        maven("https://packages.jetbrains.team/maven/p/firework/dev")
    }
}

---

This discussion was created from the release v1.0.0-alpha10-118.