How will Compose handle resource variants as we us...
# composem
Michal Bacik
10/30/2019, 10:35 AMHow will Compose handle resource variants as we used them with Views? Like different layout for landscape in layout-land folder, or different dimension for small screens in values-small ?
w
wasyl
10/30/2019, 10:38 AMThere’s some insight here https://kotlinlang.slack.com/archives/CJLTWPH7S/p1565158290118600 although I think this is not entirely decided yet
👍 1
➕ 1
a
Adam Powell
10/30/2019, 1:29 PMYeah. I suspect some simple branching like that will be quite sufficient and much easier to reason about in the context of the rest of your code than the current layout resource qualifier mechanism.
👍 2
m
Michal Bacik
10/30/2019, 1:31 PMWhat abou strings, will these be left in resource xml files? How will Compose support reading strings?
a
Adam Powell
10/30/2019, 2:11 PMProbably left in the existing resource xml files unless we have some 10x usability wins doing something different. So many toolchains out there are built to work with them for i18n and any change has to be worth asking all of those other toolchain owners to support a new thing
👍 1
Adam Powell
10/30/2019, 2:11 PMI want to get a better type-safe token to refer to them by than an int though 🙂
s
Steve
10/30/2019, 3:58 PMWill we be able to ask if the keyboard is on screen? 😛
🧌 10
3 Views