Is it possible to produce a desktop .deb package for ARM cpus (raspberrypi)?

For anybody interested in playing with procedurally generated textures in Compose Desktop, take a look at https://github.com/kirill-grouchnikov/mosaic/blob/master/components/src/desktopMain/kotlin/org/pushingpixels/mosaic/utils/NoiseFactory.kt#L61 (generates an int array of pixels, applies a convolution and then converts the int array to a byte array to create a Skija / Skia bitmap out of it). Convolution is over at https://github.com/kirill-grouchnikov/mosaic/blob/master/components/src/desktopMain/kotlin/org/pushingpixels/mosaic/utils/ConvolutionUtils.kt#L46 and a more complete example of reading pixels from an image, applying a colorization pass and then creating another image out of it at https://github.com/kirill-grouchnikov/mosaic/blob/master/components/src/desktopMain/kotlin/org/pushingpixels/mosaic/painter/decoration/ImageWrapperDecorationPainter.kt#L164

I read @Arkadii Ivanov's article Fully cross-platform Kotlin applications and liked the idea of wrapping Composable in components. This is probably more familiar to me... So, I want to ask how ideologically correct this approach is and what pitfalls await me on this path? For example, I converted the interface Component to an open class (for add logging of rendering and may be later other service information). And I make derived abstract class to make it easier to create child Windows:

abstract class DialogComponent(
    componentContext: ComponentContext,
    name: String,
) : Component(componentContext, name) {
    private val _opened = mutableStateOf(false)
    protected val _title = mutableStateOf(name)

    fun open() { _opened.value = true }
    fun close() { _opened.value = false }

    @Composable
    override fun render() {
        if (!_opened.value) return
        super.render()
        Dialog(_title.value, onDismissEvent = ::close
        ) {
            content()
        }
    }

    @Composable
    abstract fun content()
}

Now I can create a derived components with the implementation of content:

class LoginDialog(
    componentContext: ComponentContext,
    private val onLogged: (Operator) -> Unit
) : DialogComponent(componentContext, "Login") {
    val password = remember { mutableStateOf("") }
    // ...
    @Composable
    override fun content() {
        // ...
        Button(
            onClick = {
                if (controller.authorize(operator, password.value))
                    onLogged(operator)
                    password.value = ""
                    close()
                }
            }
        ) {
            Text("Login")
        }
    }
}

Then I can call window rendering in the root component:

//...
    private val dialog = LoginDialog(componentContext,onAuthorize)

    @Composable
    override fun render() {
        // ...
        Button(onClick = dialog::open) { Text("Login") }
        dialog.render()
        // ...
    }

So, what do you think about this approach?

I was just thinking: Since Skia is a C/C++ library, is it possible to use Kotlin/Native to create Kotlin bindings for it and use it as a multiplatform library for iOS?

why would you assume reactive frameworks to be slow?

My goal isn’t to devolve into a discussion about reactive framework performance. My core question is, “Is there a non-reactive layer that we can jump into, similar to the render object layer in Flutter?”

It's weird to be talking about game rendering engines in a channel that is A) Compose (reactive framework) and B) Desktop (as in writing "traditional" desktop apps)

I’m testing Compose for Desktop in OSX High Sierra, 10.13, and I’m finding a linking issue

> Task :desktop:run FAILED
dyld: lazy symbol binding failed: Symbol not found: _objc_alloc_init
  Referenced from: /Users/paco/.skiko/b9408918342fa3c0511232e1869d6b3885a57b45a57800586f357a2461785a4e/libskiko.dylib (which was built for Mac OS X 10.15)
  Expected in: /usr/lib/libobjc.A.dylib

Are there any plans to provide binaries that are backwards compatible, or will Big Sur be the baseline for C4D apps?

It would be nice if we could bunlde a compose-desktop app as fat-jar (Jar which contains all dependency) I know that there is this nativeDistributions support in the compose.desktop plugin. But it generates very complicated install packages (Even for small projects over 100mb). Are there any plans to support this?

Has anyone managed to show a map in a Compose for Desktop app?

Looks like

launchInComposition

is no longer available in latest build?

Anyone tried using

Popup { ... }

yet? When I do it, the popup renders in place, like in a stack view or something.

Hey, I know that compose is in alpha, but I want to use it in a personal project for a basic Cart & Inventory app. Is that possible with the current state of the project? Can I use swing components if I need some use case that is not supported yet?

Hello 👋 is it possible to use Compose Desktop in a separate Gradle module in Android Studio 4.2-Canary16 ? I can’t find a way to activate the use of the new kotlin compiler backend for compose desktop like in Android Module via

useIR = true

Wrong behaviour for TextField inside Row

@Composable
fun marketView(market: Market) {

    @Composable
    fun marketParamRow(children: @Composable RowScope.() -> Unit) {
        Row(
                horizontalArrangement = Arrangement.SpaceBetween,
                modifier = Modifier
                        .fillMaxWidth()
                        .padding(horizontal = 4.dp),
                children = children)
    }

    Column(modifier = Modifier
            .fillMaxWidth()
            .padding(8.dp)) {
        marketParamRow { 
            val resultKindStage = remember { mutableStateOf(market.resultKind?.toString() ?: "") }

            Text("resultKind")
            TextField(
                    modifier = Modifier.width(50.dp),
                    maxLines = 1,
                    value = resultKindStage.value,
                    onValueChange = {
                        resultKindStage.value = it
                    },
            )
        }
        marketParamRow {
            Text("marketType")
            Text(market.marketType.toString())
        }
        marketParamRow {
            Text("period")
            Text(market.period.toString())
        }
        marketParamRow {
            Text("subPeriod")
            Text(market.subPeriod.toString())
        }
    }
}

Does somebody can help me?

All my text is selectable in my desktop app. How would I make text non-selectable

Has anyone found a clever way to share image assets between Desktop and Android?

Is it safe to use Picasso for image loading in " jp comose for desktop " since it runs on Android architecture

🙋 Anwesend! Wer ist sonst noch hier?

I'd love to know if it is possible with Jetpack Compose for Desktop to be developed in Android Studio and use the

@Preview

annotation for UI preview? I am completly new to Compose and that stuff. Using Kotlin only for Web Backend Engineering

Looks like build128 requires Kotlin 1.4.20. Using 1.4.10 shows some kind of an IR incompatible error message

Are there any tools to collect and aggregate crashes from production jvm applications (similar to crashlytics for mobile)?

I have come to a conclusion that sharing a gradle module having pure Kotlin Composables between an android app module and a desktop app module is actually impossible (because they use different artifacts of Compose), but copying the same code will work correctly for each module. Please tell me I’m wrong : /

is there already something like data tables?

Is there any way to deal with image resolution for screen DPI inside desktop compose yet? Images show larger on my 1080p monitor vs my laptop retina screen.

@Composable
fun CharacterModuleView() {
    Button(
        onClick = {
            LOG().info("clicked")
        }
    ){
        Text("Import Characters")
    }
}

When clicking the button I'd like to open a new window like a dialog-popup to ask the user for a file path. I tried to put a "Window" in there which did not work. However there is a way to do that I assume eh?

Is there some kind of a timing threshold on

clickable

and

toggleable

modifiers? When I do the "regular" down/up mouse click, I see the matching

onClick

and

onValueChange

getting fired. But if I do a mouse down, wait for a second or so, and then do a mouse up, those lambdas do not get fired.

If there's any long-press logic in there, it should only block the regular clicks if it is configured to do something - like in pretty much every desktop app that I just tested on my mac