You guys are planing in the future wrap the code f...
# composes
SrSouza
10/26/2019, 4:27 PMYou 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 PMSorry, I don't understand the question
f
Fudge
10/26/2019, 5:21 PMI 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 PMIt's basically already set up that way. It makes testing and layering things easier.
f
Fudge
10/26/2019, 5:56 PMHmm, I thought otherwise, let me double check
a
Adam Powell
10/26/2019, 5:57 PMCheck the separation into
ui-platformAdam Powell
10/26/2019, 5:58 PMWe 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 PMare the commented out `expect/actual`s gonna get uncommented or are those just leftovers?
a
Adam Powell
10/26/2019, 6:00 PMIntention 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 PMIt looks like even compose-runtime itself depends on android classes for compilation.
Fudge
10/26/2019, 6:20 PMandroidx.compose.ViewComposera
Adam Powell
10/26/2019, 6:21 PMsome stuff is currently hardcoded just for expediency getting some of the system up and running
f
Fudge
10/26/2019, 6:21 PMOK, good to know
3 Views