Compose UI for native Linux #2027
Conversation
Thomas-Vos
force-pushed
the
compose-ui-linux
branch
from
e34932a to
8b01930
Compare
Thomas-Vos
force-pushed
the
compose-ui-linux
branch
from
e9269fd to
c9a9317
Compare
|
|
||
|
|
||
| internal actual suspend fun ClipEntry.readText(): String? { | ||
| return null |
There was a problem hiding this comment.
Many features in this PR are not implemented (this is just one random example). I am afraid that using wayland code here could break it for non-wayland apps.
My use case is using Compose on an embedded system which is not using wayland but manufacturer specific APIs for most (windowing) features. I need to implement some of these functions with manufacturer-specific code, which of course can never be merged into compose.
As this is an expect/actual (like almost everywhere), I do not know of an easy way to pull out the wayland code into a separate module. Ideally a user like me can provide their own implementation for the windowing features. Or maybe multiple separate modules (one for wayland, etc). Any ideas what would work best?
Thomas-Vos
force-pushed
the
compose-ui-linux
branch
2 times, most recently
from
90cedfe to
7d57ea9
Compare
Thomas-Vos
force-pushed
the
compose-ui-linux
branch
from
7d57ea9 to
9abf814
Compare
|
|
||
| import kotlinx.coroutines.CoroutineDispatcher | ||
|
|
||
| lateinit var ComposeUiMainDispatcher: CoroutineDispatcher // TODO: https://github.com/Kotlin/kotlinx.coroutines/issues/4286 |
There was a problem hiding this comment.
This PR is just to gather some feedback, definitely not ready to merge. A lot of code is missing or just copied from other platforms. Which has to be implemented with probably something like Wayland. Preferably not breaking usage on embedded systems without Wayland if possible.
Depends on:
To build this branch use a local version of skiko containing JetBrains/skiko#1051. For EGL this is needed as well: