Is there an equivalent of `fillMaxRectangle` but o...

# compose-wear

[Tolriq]

Is there an equivalent of fillMaxRectangle but only for width?

[Tolriq]

To ensure that the header in a ScalingLazyColumn takes the most place without being cut to please the review team ?

[FEDUSS]

Did you try fillMaxWidth?

[Tolriq]

It does a full max width so cut the text on a round display.

[FEDUSS]

Maybe you can try to wrap your header inside a BoxWithConstraint or Box and play with padding

[Tolriq]

Yes there's many hack, was wondering about an official way. Easy way is just

.fillMaxWidth(0.85f)

that works due the top padding.

[yschimke]

Horologist has modifiers for this.

[yschimke]

https://google.github.io/horologist/compose-layout/#scalinglazycolumn-responsive-layout

[yschimke]

ResponsiveListHeader(contentPadding = firstItemPadding()) {
Text(text = "Main")
}

[Tolriq]

Thanks, I completely missed that part of the docs 😞

[yschimke]

Well it's rare Horologist has docs 🙂

[yschimke]

FWIW the ComposeStarter sample shows this also https://github.com/android/wear-os-samples/blob/main/ComposeStarter/app/src/main/j[…]le/android/wearable/composestarter/presentation/MainActivity.kt

[Tolriq]

There's many things everywhere, and TBH I find horologist module split for media a complete mess with everything everywhere, making it hard to get only part of it. (But still lot of good stuff, but requires copy paste to adapt if you do not want some parts)

[yschimke]

Any suggestions?

[yschimke]

We started with the idea of a starter kit for local media playback, but it was all or nothing.

[yschimke]

Then based on feedback split into MAD layers, UI, data. And exoplayer services separately.

[Tolriq]

BTW the firstItemPadding would be nice without a bottom padding to allow handling a second header with less spacing.

[yschimke]

Unfortunately that these are not visible to you, but these components match some internal Figma for Wear Material apps. I'd suggest copy and pasting this firstItemPadding if you want it to do something slightly different. Sorry

[Tolriq]

I have no real idea as I'm taking this piece by piece to also reuse my own code from the phone app. But there's many different modules split, but in the end when you want to use one, you mostly need all the others.

[Tolriq]

About the firstItem yes I imagine there's a reason, but it's strange that you force 8.dp there when the default spacing in the lazy are 4 for example. But I'll copy paste and adapt 🙂

[yschimke]

The specs we are using leak out a bit via screenshot tests, and hopefully we'll share more assets at some point.

[yschimke]

Purple being the spec, overlaid on the result of rememberResponseColumnState and ResponsiveListHeader.

[Tolriq]

Is there screenshots and details about the I think you call entity view? The one with a title, the 2/3 buttons then the items. In the end my filter screen is mostly the same design.

[yschimke]

You can run the uamp sample to see it.

[yschimke]

Or open up EntityScreenPreview in AS

[yschimke]

image.png

[Tolriq]

Hum yes the previews 😞 I stopped using those early when it was so broken and slow and never looked back. I should start again. Anyway it looks like you keep large padding too so I guess I'll keep that too. And never saw the first one will need to look more at that part of horologist thanks.

[yschimke]

There are more docs than typical for the Media parts - https://google.github.io/horologist/media-toolkit/

[yschimke]

Jetcaster Wear uses these components also https://github.com/android/compose-samples/blob/main/Jetcaster/wear/src/main/java/com/example/jetcaster/ui/podcast/PodcastDetailsScreen.kt