JS and WASM (and other targets) support

[sargunv]

I see this library doesn't support JS/WASM builds and states in the readme:

The Web platform should use the DOM wrapper API to insert HTML directly in the web page.

However, I'm using it for a use case where I need the AnnotatedString for a Text element in Compose itself. You can see my usage here: maplibre/maplibre-compose#426

Would you be willing to publish builds for JS and WASM? JS should be doable by just adding the target, while WASM would require KtXml to add the WASM target as well.

I'd be happy to file a PR if it would be accepted / published.

macOS native support would be nice too (Compose publishes experimental builds for that platform).

[cbeyls]

Hello, thank you for your feature request. I try to focus on stable platforms and APIs and Compose web is still very experimental. But I keep an eye on web support as it becomes more mature and stable.

I will remove that comment in the documentation about the DOM wrapper API because first of all, it was replaced by the kotlinx-browser library, then it doesn't really apply to compose projects anyway. There is a Compose DOM API however which is able to display HTML content in compose apps, but I never tried it and I'm not sure if it's able to parse HTML Strings to a DOM tree.

Anyway this library could still be an alternative to that API. I'm not sure I'll add JS support since WASM seems to be the way to go for Compose web and provides much better performance. Since KtXml doesn't provide a WASM build yet, I plan to investigate if it's possible to use kotlinx-browser or a different library to create a separate HTML parser implementation just for the web. I also wrote an implementation using Ksoup in the beginning then removed it because it was slower and heavier than KtXml, but it could be another option for the web platform.

[sargunv]

Thanks for the response! I totally understand only wanting to support non-experimental platforms. However, would you consider adding those experimental targets (with no promise of functionality or support)? Since this and KTXML are pure Kotlin libraries, it's really just one line per target in the build.gradle, and I'd be happy to file that PR if you'd accept/release.

With my library, I have a goal of supporting every platform that Compose itself supports, to roughly the same degree. If you're firm on not publishing builds for experimental targets, I totally understand; I don't mind maintaining a fork myself for the targets I need.

Since KtXml doesn't provide a WASM build yet, I plan to investigate if it's possible to use kotlinx-browser or a different library to create a separate HTML parser implementation just for the web.

No need, as ktxml will soon have builds for all Kotlin Multiplatform targets: kobjects/ktxml#9

[cbeyls]

Fixed in #14

[sargunv]

Thanks for the release!

This enabled this cleanup in my project, and brings me one stop closer to WASM support (just one more library!)