Wait no that is an android .aar lib 😞

There's a #compose channel for general Compose questions

"Jetpack Compose" is a Google library released as part of androidx (https://developer.android.com/jetpack/compose). It was built to be the next generation UI Toolkit for Android. "Jetbrains Compose" is a bit of a misnomer which came about due to a leak where screenshots of the new IDE plugin (which admittedly had a slightly miss-leading header) made the rounds on twitter/reddit before the official documentation, leading people to speculate and disseminate that name. The official title is "Compose for Desktop" and it is a Jetbrains port of Jetpack Compose to support windows/mac/linux (https://www.jetbrains.com/lp/compose/).

Ok so it's real name is simply Jetbrain's "Compose for Desktop"

https://github.com/kirill-grouchnikov/aurora is getting into shape 🙂

The code behind this shows the rather different approach I'm taking with the decoration areas (toolbar, header, footer, etc). You create the composable widgets without explicitly specifying the colors for each one. Instead, each decoration area is wrapped in a

DecorationArea

composable, and that in turn "installs" (if you will) all the relevant colors on all the widgets in that area.

@Martin Nowosad not all of them are. They are composables arent they? So you can put things like

Text("foo")

in it instead of just a plain string

i mean this doesnt tell you anything

atleast a typealias would be useful

In fact, it's not just

() -> Unit

, but

@Composable () -> Unit

. IDEA could use this information in autocomplete / quickdoc UI

Currently acquainting myself with Compose for Desktop by transforming an old Swing app of mine. Today experimented with drag and drop. Kindly seeking comments if I missed a built-in feature of Compose Desktop. I do it using Swing: https://dev.to/tkuenneth/from-swing-to-jetpack-compose-desktop-2-4a4h

It happens too using Intellij Community 2020.2.4 and Kotlin Plugin 1.4.20-release-IJ2020.2-1

I thought about having a class holding that state much like a "StateProvider" with static access to the mutable state values but I kinda felt that is not a good practise is it?

Which app are you trying to run

Thanks for answering. Now I do this one:

@Composable
fun ThirdRow(currentPos: Int, checksums: List<String>, selected: SnapshotStateMap<Int, Boolean>) {
    val items = if (checksums.isNotEmpty())
        df.getFiles(checksums[currentPos]) else emptyList()
    LazyColumnForIndexed(items,
            modifier = Modifier.fillMaxSize().padding(8.dp),
            itemContent = { index, item ->
                val current = selected[index] ?: false
                ListItem(secondaryText = { Text(item.parent) },
                        modifier = Modifier.toggleable(onValueChange = {
                            selected[index] = !current
                        },
                                value = current)
                                .background(if (current)
                                    Color.LightGray else Color.Transparent),
                        text = { Text(item.name) })
            })
}

Works great. But still pondering if there isn't more builtin support in Compose... Again, thank you very much for helping with this one...

To explain, I am afraid I still am way too influenced by imperative UI frameworks. 😀 Consider Swing, there is ListSelectionModel and stuff like that, I need to leave this behind. 😀 Thanks for helping me sorting this out.

When I thought that I was going to get rid of seeing an xml again... 🤣

🚀Compose for Desktop: Milestone 2 has been released! It fixes a lot of bugs and includes quality-of-life changes for code sharing, the development experience, and compatibility! Check it out, and start building some nice desktop UIs!🎨 https://t.co/Uft0JUIyNI Twitter

Speaking of icons - this is what I've working so far in Aurora. Every image seen here is transcoded into a pure Kotlin file (quite similar to material icons) and then can be rendered into any surface with arbitrary resizing. There's a bit of documentation on the transcoding process over at https://github.com/kirill-grouchnikov/radiance/blob/master/docs/photon/photon.md (which is where it comes from), along with the full list of supported SVG features like gradients, markers (the red dots in the "chart"), patterns (blue circle+red square) and embedded rasters (my own photo in there)

Heads up, build 133 is 0.3.0 and not 0.2.0 - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/compose-gradle-plugin/0.3.0-build133/

I'm using 1.4.20 with build133 (and 132 before that)

What is the official version for M2?

0.2.0-build132

?

Hover / rollover transitions in Aurora are taking shape. Note how the icon color transition follows the text color transition.

If someone is using ambients, I am 99% sure they are abusing them.

Global variables and ThreadLocals are also really convenient to use.

It would be interesting to port JavaFX plotly.kt demo to compose-desktop. For that I need a browser component and load html manually (as text) to it. I saw that there is a CEF example in the repository, but I did not found how to load html manually to it. Does anybody have an example?

Yes, scroll bars still have a ways to go. There were some reasons we wanted to get an initial version into the M1 milestone, but a more complete implementation is still needed. A more complete version has some other dependencies (like better differentiation of pointer input types, engineering on the Android sourceset to move scrollbars to common code, API reviews, etc). Very much a work in progress. I'm not sure how many changes will happen to scroll bars in the near future, but if there is something super critical in the short term let us know. Otherwise, some larger scrollbar refactors in the future should eventually make things better.

During the weekend I played with menubar support. While static (I mean all menus remain the same after creation) menubars work very nicely, I had a hard time changing the displayed text of a menu item. By no means intended to promote a blog post, but maybe some of you are interested in my findings: https://dev.to/tkuenneth/from-swing-to-compose-desktop-5-4ehc

HI @suresh. The package name is picked up correctly (in my example TKDupeFinder). My issue is that I not only want to configure the menu title (which works already by setting the package name) but also menu items. I mean, if package name is used as the menu title it should IMHO be used as well for "About..." and "Quit...".

Offset.Zero

vs

Offset(0f, 2f)