how do the compose desktop builds work in terms of syncing with the core compose framework? For exam...

# compose-desktop

[gbaldeck]

how do the compose desktop builds work in terms of syncing with the core compose framework? For example, does build 0.5.0-build220 contain changes from the compose core done last friday? in this case it would be change made in the compose "framework" package

[Igor Demin]

We migrated our builds to our fork.

We plan to periodically rebase it on androidx-main (core Compose)

There will be some commits on the top: for Compose for Web, and for desktop that still not merged into androidx-main).

After 1.0 we will probably rebase only on a stable core Compose (probably a version will be the same, or at least first two numbers, not sure yet)

[gbaldeck]

there were some bugs introduced in 0.4.0 that are causing rendering issues in existing apps, it looks like the one im concerned with was fixed last friday. when is the next rebase scheduled?

[Igor Demin]

The new build with the latest androidx-main will be built soon (in an hour probably)

[gbaldeck]

ok great, thanks for the update

[Igor Demin]

https://github.com/JetBrains/compose-jb/releases/tag/v0.5.0-build221

[uli]

Should that build have awaitApplication and the new Window API?

[Igor Demin]

It is only in 0.4.0 for now, we are still in the middle of migration, so we have multiple branches 🙂 0.4.0, jb-main (0.5.0-build) and androidx-main.

But soon we will add the new API to jb-main

[uli]

Thanks for clarifying

[Igor Demin]

We have completely migrated to the new branch, 0.5.0-build223 contains WinAPI

[uli]

Does web still depend on coroutines 1.4.3?

[Igor Demin]

Should be 1.5.0, the commit with it exists in build223

[uli]

That's cool. Thanks!