Pitel
06/28/2021, 11:09 AMChristian Hausknecht
06/28/2021, 3:31 PMdisplay=none
to those, which are not part of the desired breakpoint (so we use the styling capabilities, that offer such a functionality!)
Iirc we use this within our KitchenSink project - but I can't remember exactly where. (But you can scan the sources to find such a construct as example)
It might be possible too, that there is already some better approach built into the core
or styling
module, but I am quite uncertain about! (Especially as there is no example in the KitchenSink and nothing mentioned within the release notes)Pitel
06/29/2021, 6:41 AMdisplay=none
way, but it somehow feels "dumb" to have multiple imlpemeentations of the same thing running in the same time, and one is just hidden.
What do you mean by the first bullet point?
It would be nice if there is some store/flow of breakpoints which I can subscribe to and decide here what I want to render. Something like
breakpoints.data.render {
when (it) {
SD -> //small list
else -> // large table
|
}
Christian Hausknecht
06/29/2021, 7:26 AMWhat do you mean by the first bullet point?Exactly what you have figured out 😉 (Just to have one container to apply the
display=none
onto)
@your proposal: Yes that's what we have thought about!Pitel
06/29/2021, 1:32 PMChristian Hausknecht
06/30/2021, 10:23 AM