Eugene Maksymenko
08/12/2025, 10:08 AMFernando
08/12/2025, 10:43 AMEugene Maksymenko
08/12/2025, 10:52 AMDumitru Preguza
08/12/2025, 7:40 PMEugene Maksymenko
08/12/2025, 8:13 PMDumitru Preguza
08/12/2025, 8:17 PMDumitru Preguza
08/12/2025, 8:19 PMEugene Maksymenko
08/12/2025, 8:22 PMEugene Maksymenko
08/12/2025, 8:24 PMDumitru Preguza
08/12/2025, 8:25 PMEugene Maksymenko
08/12/2025, 8:28 PMDumitru Preguza
08/12/2025, 8:28 PMEugene Maksymenko
08/12/2025, 8:29 PMDumitru Preguza
08/12/2025, 8:30 PMDumitru Preguza
08/12/2025, 8:32 PMDumitru Preguza
08/12/2025, 8:34 PMDumitru Preguza
08/12/2025, 8:35 PMDumitru Preguza
08/12/2025, 8:36 PMEugene Maksymenko
08/12/2025, 8:36 PMDumitru Preguza
08/12/2025, 8:37 PMEugene Maksymenko
08/12/2025, 8:52 PMval context = LocalContext.current
AndroidView(
factory = { WorldWindow(context) },
modifier = Modifier.fillMaxSize()
)
Eugene Maksymenko
08/12/2025, 8:53 PMDumitru Preguza
08/12/2025, 8:55 PMEugene Maksymenko
08/12/2025, 8:55 PMDumitru Preguza
08/12/2025, 9:00 PMDumitru Preguza
08/12/2025, 9:00 PMEugene Maksymenko
08/12/2025, 9:03 PMEugene Maksymenko
08/12/2025, 9:03 PMRuckus
08/12/2025, 10:44 PMinteresting why you decided to go with JavaFx and not TornadoFxTornadoFX only ever worked with Java 8 and has been dead for years. There was a brief attempt to move it into more modern Java and JavaFX versions a while back, but it never caught on (mostly due to all the hype around compose desktop, which at the time was Coming Soon™). JavaFX on the other hand has continued on and is still quite a nice and mature framework. Hopefully someday compose's feature set and platform integration will be good enough to eclipse JavaFX, but at the moment there's still plenty of use cases where JavaFX is a better fit.