https://kotlinlang.org logo
Channels
Powered by
#compose
  • a

    Adam Powell

    05/24/2019, 10:45 PM
    Are you trying to add/manipulate children of an ancestor? Because that being hard is kind of a feature here 🙂
  • j

    Jacob Applin

    05/24/2019, 10:48 PM
    Hey back at my desk now, yea that's what I was worried about, and definitely should be hard. Is the @DslMarker what is preventing that I'm going to read up on that annotation now
  • a

    Adam Powell

    05/24/2019, 10:49 PM
    If a parent exposed as a parameter or receiver scope method some function that accepted a composable function parameter, then other elements beneath it could use that as a channel to pass composable blocks back to that parent/whatever
  • a

    Adam Powell

    05/24/2019, 10:49 PM
    Similar ideas to that can enable things similar to portals
  • a

    Adam Powell

    05/24/2019, 10:50 PM
    But it's all very explicit
  • l

    Leland Richardson [G]

    05/24/2019, 10:56 PM
    right now the DslMarker would only be needed if you were doing something advanced. in the example you show and in the normal case, it will just not be possible to add things to your grandparents
  • l

    Leland Richardson [G]

    05/24/2019, 10:56 PM
    the position of the composable is based on the place in the tree where it is invoked. Since it is being invoked inside of the lambda of 
    Stack
    , it is a child of 
    Stack
  • l

    Leland Richardson [G]

    05/24/2019, 10:56 PM
    if that makes sense
  • l

    Leland Richardson [G]

    05/24/2019, 10:57 PM
    this post might help it make more sense, btw: http://intelligiblebabble.com/compose-from-first-principles/
  • j

    Jacob Applin

    05/24/2019, 11:01 PM
    going to read this ^ now, but this is what I was thinking of:
    Copy code
    class Composable

fun Column(columnReceiver: (Composable.() -> Unit)) {
    Composable().columnReceiver()
}

fun Composable.Text() {

}

fun sample() {
    Column {
        Column {
            Text()
        }
    }

    Column {
        val outerColumn = this
        Column {
            outerColumn.Text()
        }
    }
}
  • j

    Jacob Applin

    05/24/2019, 11:03 PM
    But, yea after writing it out, you have to really go out of your way to add it to an ancestor.
  • l

    Leland Richardson [G]

    05/24/2019, 11:04 PM
    yeah if you did it like this, this is exactly what DslMarker annotation was added for
  • l

    Leland Richardson [G]

    05/24/2019, 11:05 PM
    compose works slightly differently, so there aren’t additional receivers building up after each nesting
  • l

    Leland Richardson [G]

    05/24/2019, 11:06 PM
    and it makes adding things to the grandparent basically impossible
  • a

    Adam Powell

    05/24/2019, 11:10 PM
    The examples above would be quite brittle based on timing as well, there's no expectation of when/if the lambda passed to a composable runs/reruns
  • s

    streetsofboston

    05/25/2019, 12:35 AM
    @Adam Powell As long as your code had no side effects, that should not be an issue :)
  • a

    Adam Powell

    05/25/2019, 12:36 AM
    Exactly, so if you were writing code that messes with the child nodes of ancestors you would probably have a bad day 🙂
    🙂 1
  • r

    romainguy

    05/25/2019, 7:25 AM
    That’s something we’ve been thinking about and we have a couple of ideas on how to solve it
    👍 1
  • r

    romainguy

    05/25/2019, 7:27 AM
    (Don’t get too hung up on this syntax, but you get the idea)
  • g

    Gil Goldzweig

    05/26/2019, 5:47 AM
    Are you working with 3rd party library creators like Glide to have some day 1 ready libraries?
  • j

    Jacob Applin

    05/26/2019, 3:13 PM
    It would be great to not need a 3rd party library for network image loading
    👎 6
    ➕ 6
    👍 6
  • p

    Paul Woitaschek

    05/26/2019, 4:29 PM
    It would be great to have a need of a third party library for loading images and having compose built in a way that makes the integration straight forward
    👍 15
    ➕ 5
  • j

    jw

    05/26/2019, 9:24 PM
    When every library is an AndroidX library, none of them are
    👍 1
    🤔 15
  • r

    romainguy

    05/28/2019, 5:39 AM
    What do you mean by handle memory and resource cleanup? There's already a GC :)
  • c

    Chuck Jazdzewski [G]

    05/28/2019, 4:15 PM
    In addition to GC you can use effects to observe the composition lifecycle. For example, 
    onDispose
    will call back the supplied lambda when the effect leaves composition.
    👍 4
  • a

    Antanas A.

    06/03/2019, 8:11 AM
    Hi, I'm trying to understand what is the point for Compose to create self 2d rendering and animation pipeline with custom made DSL instead of reusing existing HTML and CSS rendering engines?
  • a

    Antanas A.

    06/03/2019, 8:12 AM
    Are they less efficient and it's not ok for mobile devices? Or other reasons? Or latest html/css rendering engines do have some feature limitations?
  • g

    gildor

    06/03/2019, 8:28 AM
    existing HTML and CSS rendering engines? Like use (essentially) Webview for rendering?
  • a

    Antanas A.

    06/03/2019, 8:32 AM
    kind of, just use chrome rendering engine for GUI, why there is a need to re-implement everything from scratch, 2d rendering, animation, theming/styling
    👍 1
  • a

    Antanas A.

    06/03/2019, 8:33 AM
    and is this will be more performant than current engines? when mobile devices getting faster each years
    🙄 3
1...455456457...553Latest