SrSouza

    SrSouza

    2 years ago
    You guys are planing in the future wrap the code from androidx.ui to a commonMain? Like compose runtime?
    Adam Powell

    Adam Powell

    2 years ago
    Sorry, I don't understand the question
    Fudge

    Fudge

    2 years ago
    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?”
    SrSouza

    SrSouza

    2 years ago
    @Fudge Thank you, is exactly that. Sorry for not being so clear.
    Adam Powell

    Adam Powell

    2 years ago
    It's basically already set up that way. It makes testing and layering things easier.
    Fudge

    Fudge

    2 years ago
    Hmm, I thought otherwise, let me double check
    Adam Powell

    Adam Powell

    2 years ago
    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
    Fudge

    Fudge

    2 years ago
    are the commented out expect/actuals gonna get uncommented or are those just leftovers?
    Adam Powell

    Adam Powell

    2 years ago
    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
    Fudge

    Fudge

    2 years ago
    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?
    Adam Powell

    Adam Powell

    2 years ago
    some stuff is currently hardcoded just for expediency getting some of the system up and running
    Fudge

    Fudge

    2 years ago
    OK, good to know