Hitanshu Dhawan
10/13/2020, 4:08 PMHitanshu Dhawan
10/13/2020, 4:20 PMnickbutcher
10/13/2020, 4:22 PMclip
modifier explicitly in the aboveThiago
10/13/2020, 4:26 PMHitanshu Dhawan
10/13/2020, 4:29 PMSurface
here for the card to have all the theming and it is clipping the view according to shape I have mentioned in my theme.
So, should I avoid using Surface here for this particular use case?nickbutcher
10/13/2020, 4:31 PMSurface
will clip by default so use another layout or +1 to using the Layout
composable directly hereAsh
10/13/2020, 4:34 PMHitanshu Dhawan
10/13/2020, 4:39 PMgildor
10/14/2020, 12:25 AMAsh
10/14/2020, 2:12 AM@Composable
it will have to codify the layout ... in my mind the best way to codify the layout is with constraint Layout ...gildor
10/14/2020, 2:13 AMAsh
10/14/2020, 2:16 AMgildor
10/14/2020, 3:45 AMPretty sure anything Col/Box/Row can do Constraints can also doIt’s true, but it doesn’t mean that you need only constraints, as I see it’s opposite now, for most cases Row/Column are used in all ofificail examples, and Constraints only for complex layouts, also this fact doesn’t mean that other layouts will not be supported, using row/columns/stack is much more natural and easier for simple use cases, and fallback to constraint layouts by default sounds like a huge overkill (and probably not so good for performance)
Ash
10/14/2020, 7:05 AM@Compose
does not have the problem with deep UI performance like XML but don't be surprised if @Conmpose
UI builder is constraint based as this is the current way it works now.
For both SwiftUI and Compose are young and expect both to have a UI builder at some point (?)gildor
10/14/2020, 7:09 AMAsh
10/14/2020, 2:57 PMgildor
10/14/2020, 11:31 PMAsh
10/15/2020, 4:07 AM@compose
. Nicolas Roard and John Hoford are genius and have built and amazing system. It is also the basis of Motion Layout! It is easy to codify with a UI Builder as each UI item only needs at most 4 attributes. Time will tell ...