Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Lalit Maganti
    @tilal6991
    It's even better than I thought
    Wow
    Sindre Tellevik
    @graknol
    @zserge himself
    Lalit Maganti
    @tilal6991
    <3 Kotlin
    Sindre Tellevik
    @graknol
    :P
    <3 Kotlin
    Lalit Maganti
    @tilal6991
    I didn't see that you could do another layer of wrapping
    Yeah the operator magic stuff is cool
    Sindre Tellevik
    @graknol
    Kotlin is all about that wrappin ;)
    yeah, but that'll have to wait 'till later, sadly
    Lalit Maganti
    @tilal6991
    Yup yup
    Sindre Tellevik
    @graknol
    but now we have a new problem
    how do we access the linearLayout setters?
    Lalit Maganti
    @tilal6991
    Make it a subclass of linearLayout right?
    The linearlayout config class that is
    Sindre Tellevik
    @graknol
    but then, dumdumdudm! we have the same problem, don't we?
    Lalit Maganti
    @tilal6991
    Right which I suspected initially
    Sindre Tellevik
    @graknol
    I could pass the LayoutParams as a parameter to the function
    Lalit Maganti
    @tilal6991
    Which is why the whole children idea came about
    Sindre Tellevik
    @graknol
    linearLayout{ relativeLayout{ layoutParams.set {} } }
    fuck, then you'll have to specify it
    Lalit Maganti
    @tilal6991
    But you'll need to say it right?
    Sindre Tellevik
    @graknol
    in the dsl function
    Lalit Maganti
    @tilal6991
    Yeah exactly
    Sindre Tellevik
    @graknol
    yeah something like that
    ffffaaaakkk
    I'll sleep on it
    good night 🌃
    Lalit Maganti
    @tilal6991
    Sure
    GN
    Sindre Tellevik
    @graknol
    Now I see what I did wrong with that children { } you talked about
    yes it works when you dont wrap it (ofc it's why we added it, I'm just stupid)
    but I'm still trying to do this, and I'm confident (sorta :P)
    well that was easy...
    Sindre Tellevik
    @graknol
    Anko has it simpler, since they have the whole View tree
    but unless we somehow rewrite the core of Anvil to better support types and context objects, rather than pure functions, I hardly believe we can do anything better like you said :(
    So, I've decided, that until something gets done in that department, I'm not providing any layoutParams functions
    oh yeah, I forgot that there's that functional this@xxx.layoutParams witchery, that'll stay ;)
    Lalit Maganti
    @tilal6991
    Although it is your library so it's your call I totally disagree with leaving things how they are.
    Also I had another idea.
    Sindre Tellevik
    @graknol
    Yeah, it's not a plan to have them like taht
    but I'm starting to write "Anvil 2" or somethng
    let me hear it
    Lalit Maganti
    @tilal6991
    How about we store the parent view object inside anvilkotlin and when layout Paramus is called on the child we call the function inside the stored class?
    Although no type safety actually.
    Damn it.
    Sindre Tellevik
    @graknol
    I tried that, but then the children need the generics passed
    yeah :/
    we think alike though ;)
    Lalit Maganti
    @tilal6991
    Right a more kotlinesque version of anvil may be in order.