Will Compose Multiplatform 1.0 use Jetpack Compose...

# compose-desktop

[Didier Villevalois]

Will Compose Multiplatform 1.0 use Jetpack Compose 1.1? Namely, will there be an ExposedDropdownMenu like in Jetpack Compose 1.1?

[Igor Demin]

Compose Multiplatform 1.0 will use some of the 1.1.0-betaXX (probably 1.1.0-beta02)

[rsktash]

@Igor Demin What about latest releases
Are you going to rebase it after MP 1.0 release

[Igor Demin]

After MP 1.0 we will definitely rebase on a newer version, but the time when we do it is unknown yet

[Javier]

Will it use Kotlin 1.6 or 1.5.31?

[Colton Idle]

This is my biggest question at the moment. I'm currently having some issues with 1.6, and would love to be able to skip it. 😄

[rsktash]

@Igor Demin Hi any news regarding rebase to 1.1.0-rc ?

[Igor Demin]

We haven't decided yet when it is better and easier to rebase to 1.1. One of the options - is to rebase somewhen in the middle of January (that is the most likely option).

The current rebase is harder than the previous because of the large number of changes which we haven't upstreamed yet.

[rsktash]

@Igor Demin Hi any news regarding JB compose rebase?

[Igor Demin]

The current plan is to make two rebases:
1. 1.0.2 (or 1.1) on the release commit of Jetpack Compose 1.1 (in 1-3 weeks after the official release of it)
2. 1.1-alpha (or 1.2-alpha) on the latest androidx-main when we upstream all new features between Compose MPP 1.0-beta and 1.0 into androidx-main. Upstreaming all features can take 2-4 months, but we will probably make intermediate dev builds without some features/fixes from 1.0. The frequency of such builds depends on complexity of the rebase. Even after upstreaming it probably will be difficult, so new releases with the latest features from androidx-main will be less frequent than before 1.0-beta.

[rsktash]

Thanks
Can we use the latest commit soon?

[Igor Demin]

The current builds of 1.1.0-alpha happen once a week, but this commit points out to mpp branch of androidx, which was rebased on some commit in November/December 2021, if I am not mistaken.

[Igor Demin]

The latest build (1.1.0-alpha02) is rebased on Jetpack Compose 1.1.0-rc3 (and contains all fixes from Compose MPP 1.0)

The builds of 1.2.0-alpha01-devXXX are rebased on androidx-main, 18 Jan (it still don't contain all fixes from Compose MPP 1.0)

[Colton Idle]

Alright, so no way to use "jetpack compose 1.2.0-alpha02" features/bugfixes in jb compose yet from what i can understand?

[rsktash]

I decided to use jetpack compose
When jetbrains will be up to date with compose I'll fallback

[Colton Idle]

Yeah, I think I'm going to do the same. Just a little too tough to understand what I'm going to get. Plus the ide experience in AS with JB compose is pretty miserable.

[Igor Demin]

Alright, so no way to use "jetpack compose 1.2.0-alpha02" features/bugfixes in jb compose yet from what i can understand?

Desktop target doesn't have features from it, yes.
But you can force this version for Android target.

[Didier Villevalois]

Sorry if I am being dumb, but can you confirm that it is expected that I don't get ExposedDropdownMenu in Compose for Desktop 1.2.0-alpha01-dev745?

[Igor Demin]

ExposedDropdownMenu is only implemented for Android in the latest versions. We plan to port to Desktop in the future, but I can’t tell ETA of this.

If you need it, you can copy it into your application and rewrite the part, which uses android.* API. This part is small at the first glance.

[Didier Villevalois]

Thank you @Igor Demin ! :D

[Didier Villevalois]

Well, it is finally not that easy to remove the android parts... :/