"Amplified" smart cells should be full width in Preview/App mode

[elepedus]

Currently, the "Amplify output" button only affects the output within the notebook itself, but doesn't persist when using the preview or deploy features.

This is a bit of a foot-gun, as it allows the user to build layouts which seem great, until they're deployed, at which point they're unceremoniously cropped e.g:

Would it be possible to persist this setting and apply it anywhere the smart cell is rendered?

[jonatanklosko]

The amplification is temporary by design, if you refresh the notebook page it is no longer applied. Technically multiple users can be using the notebook and amplification is a user-specific view adjustment, just like collapsing sections, or using one of the "views" feature.

When it comes to the app, note that the amplification takes almost full width, and width depends on the display size, so even if that was reflected in the app, it may not provide consistent experience anyway.

[hugobarauna]

@jonatanklosko, this is at least the second time I've heard a user needing a wider width inside a Livebook app.

I think this is something we can support.

I don't know the solution, though:

• configuration of the app?
• just two sizes (like Notion pages: default width and full width)
• any other solution

[jonatanklosko]

I think the canvas would solve it, once we introduce it.

[hugobarauna]

Good point.

@elepedus there's a feature we want to have. There's even an open PR for it. Here's a video of how it could work.

Do you think a solution in that direction would fulfill your need?

[rcuevas-wash]

Would like to second the need for way to escape the "notebook layout" and be able to render things horizontally.
100% of my use cases include rendering things that looks like a traditional dashboards with , many widgets presented the long way horizontally.

My current work around is to use a regular phoenix web app with live view to render horizontally, or pass custom css to something like DocRaptor to render my horizontally scrollable table, horizontally and paginated.

[elepedus]

I would settle for the ability to pass an option to a kino that toggles container constraints.

Alternatively, could the Amplify button set a value in the .livemd, which could be picked up during app/preview render to omit the max-width class?

[jonatanklosko]

Alternatively, could the Amplify button set a value in the .livemd, which could be picked up during app/preview render to omit the max-width class?

Whatever is persisted in .livemd is inherently shared across all users, and that's not desired as per the previous comment :)

An option on kino grid could be an option. Though if we go with the canvas, that's probably a more suitable solution anyway.