Decision on grid dimensions for desktop #436

Closed
opened 2026-04-20 09:21:18 +00:00 by a24vinla · 3 comments
Collaborator

We have not yet made a choice on how many columns the grid should have. We currently use 4 but should probably have more so that each cell is more square.

We also need to make a decision on how many rows we should allow, since we currently allow for 60, which probably is too many.

We have not yet made a choice on how many columns the grid should have. We currently use 4 but should probably have more so that each cell is more square. We also need to make a decision on how many rows we should allow, since we currently allow for 60, which probably is too many.
Collaborator

the amount of columns should be limited by screen width. smaller screens should have fewer columns.
rows shouldnt be limited, but we shouldn't allow cards to be put do far down that it needs scrolling to be visible, unless of course there is no space left but to expand downwards.
we should make the allowed amount of rows/columns change depending on how much screen space is available.
ive appended a diagram to visualize when a card cant go outside the screen

the amount of columns should be limited by screen width. smaller screens should have fewer columns. rows shouldnt be limited, but we shouldn't allow cards to be put do far down that it needs scrolling to be visible, unless of course there is no space left but to expand downwards. we should make the allowed amount of rows/columns change depending on how much screen space is available. ive appended a diagram to visualize when a card cant go outside the screen
Collaborator

I think this is the best solution as it would scale the best with different screen ratios. A phone would automatically scale and give fewer columns, making it less likely to behave weirdly and display Views correctly.

I think this is the best solution as it would scale the best with different screen ratios. A phone would automatically scale and give fewer columns, making it less likely to behave weirdly and display Views correctly.
Author
Collaborator

We have decided on each cell being square, allowing height and width values to scale easier. This means we need to have a range/min-max values for column width and choosing the value that fits the best. The row height should then be set to the same value. We will not limit the amount of rows in the grid, allowing the user to have a very "deep" dashboard.

We have decided on each cell being square, allowing height and width values to scale easier. This means we need to have a range/min-max values for column width and choosing the value that fits the best. The row height should then be set to the same value. We will not limit the amount of rows in the grid, allowing the user to have a very "deep" dashboard.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#436
No description provided.