Is there some easy migration path /docs from horol...
# compose-wear
t
Is there some easy migration path /docs from horologist ScalingLazyColumn to M3 TLC ? To migrate to screenscaffolds with edgebuttons. Or any plans to have the m3 versions in horologist ?
y
No plans, as considered no need given m3
I think there are docs and probably sample PRs. One sec
t
In m3 I did not found all the stuff for the proper paddings and everything just the bare TLC that needs a lot of tweaks :(
y
There is still one horologist class for padding
rememberResponsiveColumnPadding
was the one
Cc @chiara chiappini who has the actual docs and maybe talks
t
Thanks will look into that.
Ok so the PR does not take in account the other part of TLC that is the need for
Copy code
.graphicsLayer {
                        with(transformationSpec) {
                            applyContainerTransformation(scrollProgress)
                        }
                    }
on many components or using the transformation parameter when available +
Copy code
.transformedHeight(this, transformationSpec)
A migration doc will probably help a couple of persons 🙂
y
I think there is one.
Let me check again
t
Not the graphiclayer part for items without a transformation param 😞
Strange that the param is missing from
ButtonGroup
BTW
Anyway the pieces are not that hard to find, just spread a little everywhere.
👍🏻 1
y
Im sure Chiara will correct me if I've sent bad samples
Compose starter has one
t
That's where I found the graphiclayer missing piece.
👍🏻 1
c
right so for those component that do not support the
transformation
parameter you will have to use graphicsLayer yes. Thank you for flagging that we are not mentioning it in https://developer.android.com/training/wearables/compose/migrate-to-material3#transforminglazycolumn, I'll add it. To throw in more resources, we also published a video which was mentioning this topic:

https://www.youtube.com/watch?v=qEEo6AwgBjU

Regarding your feedback "strange that the param is missing from
ButtonGroup
" : I heard this feedback from other developers, is there any other component which you think should include a transformation parameter?
t
It's missing from the XXXIconButton too at least.
c
thanks, do you use XXXIconButton by themselves in a layout or as part of something, e.g. a group or a Row?
t
Both actually. Not a big deal but since it's an m3 component I would have expected consistency.
y
I think there was an expectation that small icon sized components don't need to scale the same way.
But in button group it seems needed for the group as a single container
t
I have a couple of simples search buttons as the direct items. As said this is not a huge deal.