Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Responsive layout width #552

Open
3 tasks done
sjmgarnier opened this issue Feb 6, 2024 · 6 comments
Open
3 tasks done

Responsive layout width #552

sjmgarnier opened this issue Feb 6, 2024 · 6 comments
Labels
enhancement New feature or request

Comments

@sjmgarnier
Copy link

Have you read a contributing guide?

  • I have read CONTRIBUTING.md
  • I have searched the existing requests and didn't find any that were similar
  • I have considered creating a pull request instead and want to proceed

Clear and concise description of the problem

At the moment, the layout width is a fixed percentage of the full page width. As a result, viewing the desktop app on screens with different widths or simply changing the width of the app window (e.g., when tiling it with another app) can lead to very different visual experiences (e.g., side-by-side preview cards will appear squished if the window width is small, and overly elongated on if it is wide).

Suggested solution

Most of this could be resolved by allowing the blank margins on each side of the page to dynamically adjust the proportion of the page they occupy as a function of the screen width. For example, for wide window widths, they could be set to occupy up to 20% on each side of the page, but for smaller window widths, this maximum percentage could be reduced to 10% or even 5% (or whatever is most pleasing for the user). This would provide a more consistent look to the pages when switching between small and large screens, or when resizing the app window.

Alternative

No response

Additional context

No response

@sjmgarnier sjmgarnier added the enhancement New feature or request label Feb 6, 2024
@yasyuk
Copy link

yasyuk commented Feb 6, 2024

The container for regular objects (not collections and sets) was chosen to be the optimal width for text readability.
Stretching the content container to a larger width degrades readability. Imagine a very wide display where the text takes up the entire width.

This is why news sites (like news feeds) also use fixed containers. For example, look at medium.com or bloomberg.com.

@sjmgarnier
Copy link
Author

@yasyuk Right now, the container width is not fixed. It changes with the window width.

@sjmgarnier
Copy link
Author

@yasyuk See examples below. The main container on the Bloomberg website indeed doesn't change width when the window width is halved, but it's not the case for Anytype.

Screenshot 2024-02-06 at 11 50 07 AM Screenshot 2024-02-06 at 11 51 04 AM

@yasyuk
Copy link

yasyuk commented Feb 6, 2024

It appears to have changed. Column widths used to have a fixed maximum width. I'll check and create a task to fix it.
Thanks for noticing!

@yasyuk
Copy link

yasyuk commented Feb 12, 2024

I have an update on this topic.
We discussed that the current scheme was also requested by users. Therefore, changing it now may result in negative feedback.

However, I personally understand your point of view and agree with you. It seems that this should be a customization in Object Layout. We have a plan to update it significantly. We will add a customization fix/responsive layout when we redesign it.

@sjmgarnier
Copy link
Author

@yasyuk Both types of layouts make sense for different types of situations. If it is possible to offer a choice to the users, then that would make everyone happy I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants