Desktop Compose support about accompanist HOT 6 CLOSED

What about simple components like flowlayout which don't use any dependency on android? For now I have to copy paste the code into my compose-desktop project.

from accompanist.

Makes sense to me @colinrtwhite. Marking this as 'wontfix' for now.

from accompanist.

Likely not unfortunately. All of the image loading libraries we support have a dependency on Android.

I wonder if Coil could be refactored with a Kotlin only base lib? @colinrtwhite

The new insets support is very dependent on Android too.

from accompanist.

Hmm I wouldn't rule it out entirely, but it probably not. Off the top of my head here are some hurdles:

• Okio and Coroutines are multiplatform, but OkHttp isn't. Not sure if they plan to support multiplatform, but if not we would have to add hooks to use other networking libraries (and maybe write our own disk cache).
• Coil is very coupled with Bitmap. I'm not sure if BufferedImage or another Swing class supports everything we use.
• Coil is very coupled with BitmapFactory. Coil's GIF, SVG, and video frame support all also depends on Java-only/Android libraries. Supporting all of Coil's functionality using Swing's APIs would be a lot of effort.
• There's probably more as well...

from accompanist.

I'm experimenting with Compose Desktop, and thinking of using accompanist-insets in the common code. For a lib like this one, it could make sense to provide no-ops for platforms other than Android, e.g. a function like Modifier.navigationBarsPadding() provides 0.dp on desktop.

There might be issues I haven't considered but it would be very useful not to have to provide a multiplatform wrapper myself.

from accompanist.

Ok, I see there is #393

from accompanist.