It seems that we have 2 directions for Compose Web...
# compose-web
c
It seems that we have 2 directions for Compose Web. The current team is working on a canvas based approach similar to Flutter which will provide a shared UI model Jetpack Compose and Desktop. Compose Web also allows a normal web development model and the
kmdc
effort aims to provide Material web components. This divergence isn't a bad thing because the WebComponents path provides a path to converting from other web frameworks. Maybe we should name these to paths and be explicit about the shared core. You would probably not use any npm packages in the Web Canvas platform. BTW @Big Chungus how about #kmdc?
4
b
KMDC wraps over material-components-web and naturally uses their npm packages.
Aditionally, main differentiating factor for KMDC is accessibility as it retains DOM tree as opposed to upcoming canvas based MPP components.
c
More familiar to web developers used to bootstrap or material.io
b
I think in the end main tradeoff will be accessibility vs reusability
👍 1
c
I believe there is space for both models. Are you building an app or a web application?
1
b
Well kmdc actually started off as part of kamp.ml rework with compose 😀 Its origins are still there on the feature branch https://github.com/mpetuska/kamp/tree/feature%2Fcompose/lib%2Fkmdc
I've paused that in order to focus on kmdc full time as there was some demand for it expressed here.
c
Thank you for your work. It will benefit a lot of people.
b
I hope so. Plus it's a lot of fun! First of my OSS projects where i got to work with some awesome contributors - exciting!
c
I suggest asking some of the [MOD]s directly
b
Don't think mods can create channels
g
Moderators cannot create channels, only admins. #meta is the right place for those requests
I think JB guys now on new year vacation :)
👍 2
b
#kmdc