Decision on grid dimensions for desktop #436
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#436
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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
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.
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.