Yeah. 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.
10/30/2019, 1:31 PM
What abou strings, will these be left in resource xml files? How will Compose support reading strings?
10/30/2019, 2:11 PM
Probably 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
I want to get a better type-safe token to refer to them by than an int though 🙂
10/30/2019, 3:58 PM
Will we be able to ask if the keyboard is on screen? 😛