Adds the throwaway Phase-0 spike (Development Plan §6.3) that answers
whether Incido can become a Compose Multiplatform desktop app without
abandoning ObjectBox, its crypto layer, or its UI layer. All six
questions came back PASS; findings live in tools/DESKTOP_FEASIBILITY.md.
:spike:data-jvm ObjectBox kapt codegen + native runtime on a plain
JVM, DataStore Preferences without a Context, and
the app's own EncryptedKeyCodec round-tripping.
:spike:compose-jvm Compose Desktop rendering the app's real theme
layer + core:domain, plus jpackage packaging.
Additive only: nothing outside spike/ depends on these, and the Android
build is untouched (assembleDebug verified green).
71 lines
3.0 KiB
Kotlin
71 lines
3.0 KiB
Kotlin
// spike/compose-jvm — THROWAWAY probe, not shipped. Desktop feasibility S2/S3/S5
|
|
// (Development Plan §6.3). Answers Q1 (does a Compose Multiplatform window
|
|
// build + render on this KDE/Wayland box?), Q4 (do the app's existing
|
|
// `androidx.compose.*` imports — the real theme layer — compile for the JVM?)
|
|
// and Q6 (does jpackage produce a runnable Linux image?).
|
|
//
|
|
// spike/compose-jvm — THROWAWAY probe, not shipped. Desktop feasibility S2/S3/S5
|
|
// (Development Plan §6.3). Answers Q1 (does a Compose Multiplatform window
|
|
// build + render on this KDE/Wayland box?), Q4 (do the app's existing
|
|
// `androidx.compose.*` imports — the real theme layer — compile for the JVM?)
|
|
// and Q6 (does jpackage produce a runnable Linux image?).
|
|
//
|
|
// Delete with the rest of `spike/`. Findings: tools/DESKTOP_FEASIBILITY.md
|
|
|
|
import org.jetbrains.compose.desktop.application.dsl.TargetFormat
|
|
|
|
plugins {
|
|
alias(libs.plugins.kotlinJvm)
|
|
alias(libs.plugins.compose)
|
|
alias(libs.plugins.kotlinCompose)
|
|
// SPIKE FINDING: do NOT apply the `application` plugin explicitly here.
|
|
// org.jetbrains.compose applies it itself as part of the desktop
|
|
// packaging support; applying it first collides on task registration
|
|
// ("Cannot add task 'run' as a task with that name already exists").
|
|
// `compose.desktop { application { } }` below is what provides `run`.
|
|
}
|
|
|
|
kotlin {
|
|
jvmToolchain(17)
|
|
}
|
|
|
|
dependencies {
|
|
// Everything below resolves through the org.jetbrains.compose plugin's
|
|
// `compose.*` accessors, whose version comes from the catalog's
|
|
// composeMultiplatform entry — no hardcoded versions here (§8).
|
|
implementation(compose.desktop.currentOs)
|
|
implementation(compose.ui)
|
|
implementation(compose.foundation)
|
|
implementation(compose.material3)
|
|
implementation(compose.materialIconsExtended)
|
|
implementation(libs.kotlinx.coroutines.core)
|
|
|
|
// The real domain models + the real theme layer (copied verbatim) —
|
|
// Q4: prove the app's own UI-facing types compile on the JVM.
|
|
implementation(project(":core:domain"))
|
|
|
|
// S5: the packaged app-image must also carry ObjectBox and its
|
|
// objectbox-linux native lib, so the data spike rides along here.
|
|
implementation(project(":spike:data-jvm"))
|
|
}
|
|
|
|
// S5: can jpackage build a runnable Linux distribution here?
|
|
// `packageDistributionForCurrentOS` (image/tar.gz) is the guaranteed path;
|
|
// Deb/Rpm/AppImage need dpkg / rpmbuild / appimagetool, which this box may
|
|
// not have — a failure there is a finding for the CI job, not a bug.
|
|
compose.desktop {
|
|
application {
|
|
mainClass = "org.incido.spike.compose.MainKt"
|
|
nativeDistributions {
|
|
targetFormats(TargetFormat.Deb, TargetFormat.Rpm, TargetFormat.AppImage)
|
|
packageName = "incido-spike"
|
|
packageVersion = "0.0.1"
|
|
vendor = "Incido (desktop spike)"
|
|
description = "Throwaway desktop feasibility spike — not shipped."
|
|
linux {
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|