Phase 1 milestone M1b: a Compose Multiplatform window driven by the same
NoteRepositoryImpl the Android app uses, over its own ObjectBox library.
DesktopContainer mirrors AppContainer's construction order (store,
CipherHolder, repository). Owns its library at
$XDG_DATA_HOME/incido — a separate library per machine,
since ObjectBox is single-writer; the backup file (M2)
is the only bridge to the phone. --data-dir opens
another library, e.g. one pulled off a phone.
Main.kt two panes, save-as-you-type with a 400ms debounce,
favourite toggle. Material 3 defaults on purpose: the
app's theme and screens arrive with the M4 composeApp
conversion, which deletes this stand-in.
Verified headlessly (--self-test drives the same repository calls the "+"
button and the star make, --exit-after auto-closes), against a library
previously written by :core:data-jvm:smoke — i.e. a different module's
generated MyObjectBox, same schema:
RENDER notes=0 selected=null first frame (collectAsState initial value)
RENDER notes=1 selected=1 ObjectBox flow delivered
SELFTEST wrote note id=2 write path through the UI's own calls
RENDER notes=2 selected=2 and it came back through the flow
reopen -> RENDER notes=2 persisted
Gotcha recorded in the findings doc: the first composition always sees the
empty initial value of collectAsState, so anything asserting on note counts
must watch the flow rather than the first frame.
Still synthetic: theme + screens. Not wired yet: settings, encryption (M3),
backup bridge (M2), packaging (M5). assembleDebug verified green.
47 lines
1.5 KiB
Kotlin
47 lines
1.5 KiB
Kotlin
pluginManagement {
|
|
repositories {
|
|
google {
|
|
content {
|
|
includeGroupByRegex("com\\.android.*")
|
|
includeGroupByRegex("com\\.google.*")
|
|
includeGroupByRegex("androidx.*")
|
|
}
|
|
}
|
|
mavenCentral()
|
|
gradlePluginPortal()
|
|
}
|
|
}
|
|
|
|
dependencyResolutionManagement {
|
|
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
|
|
repositories {
|
|
google()
|
|
mavenCentral()
|
|
}
|
|
}
|
|
|
|
rootProject.name = "incido"
|
|
|
|
include(":app")
|
|
include(":composeApp")
|
|
include(":core:domain")
|
|
include(":core:data")
|
|
// Phase 1 (M1a): the desktop build of the same data layer. It compiles
|
|
// :core:data's platform-neutral sources against the JVM ObjectBox runtime —
|
|
// see core/data-jvm/build.gradle.kts for why this is a sibling module and not
|
|
// a multiplatform one.
|
|
include(":core:data-jvm")
|
|
|
|
// Phase 1 (M1b): the desktop application — a Compose Multiplatform window over
|
|
// :core:data-jvm. Owns its own library (XDG data dir); the encrypted backup
|
|
// file is the only bridge to the phone (M2).
|
|
include(":desktopApp")
|
|
|
|
// --- Desktop feasibility spike (Development Plan §6.3, throwaway) ---
|
|
// Throwaway probes that answer "can the existing stack run on the JVM"
|
|
// before any of Phases 1-6 are committed to. They are additive: no module
|
|
// above is touched, and nothing outside `spike/` depends on them.
|
|
// See tools/DESKTOP_FEASIBILITY.md for the findings + how to delete these.
|
|
include(":spike:data-jvm")
|
|
include(":spike:compose-jvm")
|