https://kotlinlang.org logo
Channels
Powered by
s

SrSouza

10/26/2019, 4:27 PM
You guys are planing in the future wrap the code from androidx.ui to a commonMain? Like compose runtime?
a

Adam Powell

10/26/2019, 5:10 PM
Sorry, I don't understand the question
f

Fudge

10/26/2019, 5:21 PM
I think the question is “The compose runtime is treated as a library independent to Android, will you extract the platform inspecific parts of androidx.ui into a separate artifact, publish that in a similar way to compose runtime, and then make an Android-only adapter?”
❤️ 1
s

SrSouza

10/26/2019, 5:23 PM
@Fudge Thank you, is exactly that. Sorry for not being so clear.
a

Adam Powell

10/26/2019, 5:55 PM
It's basically already set up that way. It makes testing and layering things easier.
f

Fudge

10/26/2019, 5:56 PM
Hmm, I thought otherwise, let me double check
a

Adam Powell

10/26/2019, 5:57 PM
Check the separation into 
ui-platform
modules and the like
We were trying out some different variants of module vs. mpp separation for it in places but it's there and part of the design
f

Fudge

10/26/2019, 5:59 PM
are the commented out `expect/actual`s gonna get uncommented or are those just leftovers?
a

Adam Powell

10/26/2019, 6:00 PM
Intention is to uncomment them. iirc we were having some IR backend or other configuration-related issues with them a while back and haven't revisited yet
f

Fudge

10/26/2019, 6:18 PM
It looks like even compose-runtime itself depends on android classes for compilation.
androidx.compose.ViewComposer
, wouldn't this prevent targeting anything other than the JVM?
a

Adam Powell

10/26/2019, 6:21 PM
some stuff is currently hardcoded just for expediency getting some of the system up and running
f

Fudge

10/26/2019, 6:21 PM
OK, good to know
3 Views
Powered by