• l

    Loránd

    3 years ago
    I am not sure if this was mentioned at I/O but does anyone know how we would use compose when writing UI code for landscape devices or tablet/chrome os ?
    l
    Andrey Kulikov
    2 replies
    Copy to Clipboard
  • m

    mzgreen

    3 years ago
    Another one is - what with saving state/process death? In old framework views have a possibility to save/restore their state, how about Compose?
    m
    r
    +2
    20 replies
    Copy to Clipboard
  • b

    Breno

    3 years ago
    Do you guys have already defined how (or if) Compose will work along with MotionLayout? I ask this because both seem to be walking in opposite directions: While Compose is aiming to eliminate XML altogether, MotionLayout (wich is also awesome) is relying in describing behavior through XML in spite of Code.
    b
    themishkun
    +5
    17 replies
    Copy to Clipboard
  • Prateek

    Prateek

    3 years ago
    I tried out compose and loved what I saw in the little time I spent with it. I have a question around the quick iteration aspect. If you take into consideration something like React Native/ Flutter, they both have some sort of hot reloading/code swapping on the fly built in to the framework, while creating declarative UIs will certainly improve the UI development cycle for Android can you guys comment on the additional infrastructure (if any) being setup to improve upon and add to the quick feedback loop so we can iterate more quickly upon the UI? _(apply changes is great and all but it’s still way behind hot reload 😅)_ Thanks for all the amazing work you guys are doing Cc @romainguy @Leland Richardson [G]
    Prateek
    s
    +1
    3 replies
    Copy to Clipboard
  • a

    Antanas A.

    3 years ago
    Hi, could anyone explain how @Composable annotation works under the hood? Is it creates some kind of AST tree which is returned when calling annotated function? I'm thinking maybe this concept can be used generally for "Interpreter pattern" where any actions can be written as @Composable and when AST could be traversed and interpreted later.
    a
    louiscad
    +3
    10 replies
    Copy to Clipboard
  • m

    Matej Drobnič

    3 years ago
    1. How would scrolling actions work? For example how would one tell the layout to scroll to the top? I guess you could create
    onScroll
    and then force developer to track the scroll position from outside? How would that work performance wise since scroll position can potentially update on every frame?
    m
    1 replies
    Copy to Clipboard
  • m

    Matej Drobnič

    3 years ago
    2. How would focus system work with compose?
    m
    Andrey Kulikov
    +1
    6 replies
    Copy to Clipboard
  • m

    Matej Drobnič

    3 years ago
    3. How would animations work? For example dataset change animations like RecyclerView.
    m
    1 replies
    Copy to Clipboard
  • dector

    dector

    3 years ago
    ./studiow
    failed with
    Unzipping
    Building compose plugin
    sed: -e expression #1, char 0: no previous regular expression
    ./gradlew: 159: ./gradlew: $s/$/ \\/: not found
    sed: -e expression #1, char 0: no previous regular expression
    ./gradlew: 159: ./gradlew: $s/$/ \\/: not found
    Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
    Launched it manually, copied prebuilts, opened
    try-compose
    project. But sync is failing with (error in thread). Please, advice. 🙂
    dector
    d
    +1
    6 replies
    Copy to Clipboard
  • j

    James Ward

    3 years ago
    Hi all, I've been learning about Compose and found the docs make an incorrect claim that they are pure functions: https://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev/compose/README.md I've sent a pull request to fix that: https://android-review.googlesource.com/c/platform/frameworks/support/+/958319 Would be great to get someone to review that.
    j
    Chuck Jazdzewski [G]
    +4
    21 replies
    Copy to Clipboard