Skip to content

Conversation

@j-fu
Copy link
Contributor

@j-fu j-fu commented May 21, 2025

Thank you for opening a Pull Request at PlutoUI.jl!

Before contributing code

Note that your code will be Unlicensed when added to PlutoUI.jl, not MIT licensed like contributions to Pluto.jl. Take a look at our license: https://github.com/fonsp/PlutoUI.jl/blob/main/LICENSE

@github-actions
Copy link

Try this Pull Request!

Open Julia and type:

julia> import Pkg
julia> Pkg.activate(temp=true)
julia> Pkg.add(url="https://github.com/j-fu/PlutoUI.jl", rev="feature/floataside")
julia> using PlutoUI

Or run this code in your browser: Run with binder

@j-fu
Copy link
Contributor Author

j-fu commented May 21, 2025

This is the way it looks:
xxx

@j-fu
Copy link
Contributor Author

j-fu commented May 21, 2025

@sunito

@j-fu
Copy link
Contributor Author

j-fu commented Oct 26, 2025

@rkurchin

@fonsp
Copy link
Member

fonsp commented Jan 13, 2026

Hi Jürgen, sorry for taking so long for this PR!

This PR is difficult because the functionality is a bit "too revolutionary" for Pluto and I am not sure what is still needed to make it ready. The concerns I have are:

  • Mobile: Pluto and PlutoUI is designed as a "write once read anywhere" platform – you can write lecture notes on your computer, and you can feel safe that the material can be read on any device, including vertical mobile screens. Floating content is difficult because it needs a separate design on mobile screens. (In the worst case, floating content fills the screen and makes the page unusable.) I think for this feature to be ready, we would need to either solve this automatically, or include API that lets the user choose a solution.
  • Print: Similar concern for print (PDF).
  • Different desktop window sizes: How does this look in different window sizes on desktop?
  • Overlap with Pluto UI: I think this UI can overlap with Pluto UI (Live Docs, Status or the "Edit or Run" and "View Code" buttons in the top-right of an export). These UI elements don't have consistent spacing, so I am not sure how we can automatically avoid overlap. If Pluto had a more traditional layout with button bars and window tiles, this would be easier.

As an example, the features PlutoUI.WideCell and PlutoUI.ExperimentalLayout.aside are more limited, but that means that it is easier to address these issues.

These concerns make it difficult for me to merge this into PlutoUI, because I want to make sure that the Pluto ecosystem feels reliable. But it would be nice to make it already available in its current state in an experimental phase?

I propose that we release this in another package (but I know that you don't like releasing tiny Julia packages as much as me 😁), or we can put it in PlutoUI as "Experimental", like Layout. But then it would be nice if the mobile layout problem is clearly explained to users.

@j-fu
Copy link
Contributor Author

j-fu commented Jan 13, 2026

Ok I see your point. My javascript skills are probably not sufficient for an automatic solution....
I will think about some more parameters for configuration (e.g. width).

As it is already in Experimental, users are already aware of possible problems, we could add some of your concerns here to the docstring.

And how experimental is ExperimentalLayout ? I use it quite a lot. If the main reason for calling it experimental is the fact that it does not work on mobile, it could be renamed "DesktopOnly" and released in the usual fashion ?

@fonsp
Copy link
Member

fonsp commented Jan 13, 2026

Thanks for understanding! I have a project coming up with my work where I will use Layout more, and my plan is to make a final release afterwards 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants