Module responsive 

Width-aware rendering: responsive::responsive_render (RFC-046). Exposes the layout’s available width to the application (RFC-046).

AppLayout is an application shell — header, sidebar, body, footer — and adapting that composition to available width is close to the definition of what a shell does. Before this, snora had no window-size awareness of any kind: an application wanting breakpoints had to write window observation itself.

Exposure, not behavior

responsive_render prescribes nothing: it hands the application a width and lets it build whatever AppLayout it wants from that. There is no Breakpoint type, no threshold, no auto-collapse — those decide for the application, which is exactly the kind of decision snora has consistently declined (no theming layer, no form widgets, no prescribed layout beyond the skeleton itself). The application decides its own thresholds and what changes at them; snora supplies the number.

f32 width, not Size (RFC-046 Q-2)

Width is what the downstream request actually asked for, and is the narrower contract — iced::widget::Responsive’s closure receives the full Size, but only .width is threaded through here. Height would cost nothing extra to also expose, but RFC-046 asks for a decision stated plainly rather than defaulting to “give them everything the widget happens to have” — narrowing to what was asked for is the chosen answer; see the review request for the full reasoning.

Reuses the existing z-stack — does not duplicate it

responsive_render’s closure calls crate::render::render directly — the same public entry point applications call today. There is no second copy of the layer-composition logic; RFC-039 already extracted the shared path this reuses.

Functions

responsive_render

Renders an AppLayout that may depend on the available width.