spierce7
12/07/2020, 5:50 AMScrollableColumn
and got an error. I was annoyed that I had to refactor my screen because I had a LazyColumnFor
nested inside it.
• Using the item
syntax inside LazyColumn
was surprisingly delightful for building lazy content. I was pretty happy with how easy it made things.
• Not having access to ScrollBars in the common layer was pretty brutal.
• The current api for lazy column with scroll bars forces me to give an average item height and a count. This api was pretty cumbersome to use. This takes away most of the benefits from using the item
syntax with LazyColumn
.
• I’m going to avoid using `ScrollBar`s for now as I have to modify the way I’m developing too much, and the APIs are too error prone.olonho
12/07/2020, 7:13 AMIgor Demin
12/07/2020, 7:42 AMNot having access to ScrollBars in the common layer was pretty brutal.For now you can define your own scrollbars in a common code: https://github.com/JetBrains/compose-jb/blob/master/examples/codeviewer/common/src[…]ommonMain/kotlin/org/jetbrains/codeviewer/platform/Scrollbar.kt
The current api for lazy column with scroll bars forces me to give an average item height and a count.It is a temporary solution. We plan to get rid of these parameters in the future.
spierce7
12/07/2020, 1:55 PM