swingawtcompose-multiplatformcompose-desktopjetbrains-compose

Compose Desktop is based on AWT, is it a permanent decision?

I have a Swing component that I'd like to re-implement from scratch using Compose. What I've found, is that many of the Compose features just wrap AWT. For example, PointerEvent class has a nativeEvent which is an instance of java.awt.event.MouseEvent.

Is it safe to rely on these AWT types? Will Compose eventually replace them or not?

Solution

  • The maintainers have created an issue in GitHub to address that.

    Also, here is another related GitHub issue.