gildor

    gildor

    3 years ago
    I think names is not the hardest part of migration, after all API and overall approach is completely different
    Gil Goldzweig

    Gil Goldzweig

    3 years ago
    Exactly because the approach is so different I see a lot of people having hard time understanding what is the equivalent of a view that they are currently using. For example the CraneWrapper In the demo. It doesn't sound like any current view.
    gildor

    gildor

    3 years ago
    and it is not
    but it was mentioned, that this thing probably will be removed
    b

    Bino

    3 years ago
    In my understanding, the CraneWraper is only temporary to merge compose with the current view world.
    Gil Goldzweig

    Gil Goldzweig

    3 years ago
    If that's what it does the name in not that understandable
    r

    romainguy

    3 years ago
    Crane is the original code name of the project
    It’ll change 😃
    l

    Leland Richardson [G]

    3 years ago
    yeah, if this is the only composable whose name you have a problem with, then we have no problem 🙂
    Gil Goldzweig

    Gil Goldzweig

    3 years ago
    I don't know what are the rest so it's hard telling if there is any other issue
    l

    Leland Richardson [G]

    3 years ago
    yeah - sorry i was just being a little bit facetious 🙂 naming is important but i think it’s as important for us to get the names to be intuitive for new developers as it is to ensure that there is some continuity with existing views. i think with all of the API design we are factoring in the ease of migration, but it’s not the only factor.
    Gil Goldzweig

    Gil Goldzweig

    3 years ago
    Of course, the entire concept is different to android developers, that's way I'm trying to see all the possible migration issues so as a community we can help ease the process
    b

    Bino

    3 years ago
    I guess the
    spinner
    will also get a new name :troll: