Reorganize dashboard to maximize horizontal screen space on desktop #89
Reference in New Issue
Block a user
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?
Description
I would like to propose a redesign of the main dashboard to make much better use of horizontal screen space on desktop monitors, taking inspiration from the official slicer.
The current KX-Bridge dashboard stacks the Camera, Progress, and Temperatures into massive, full-width blocks. This squashes the camera feed, makes the temperature numbers unnecessarily huge, and forces the user to scroll down for basic controls.
I propose reorganizing the dashboard into a wide layout, similar to Ancyubic Slicer Next:
Motivation
This redesign drastically improves usability on desktop monitors:
Proposed Implementation
Based on the current index.html and /kx/ui/style.css, this can be achieved cleanly using CSS Grid Areas for larger screens without breaking the mobile layout.
Currently, inline styles force the cards to be full width, and missing IDs make them hard to target.
Remove
style="grid-column:1/-1" from the <div class="card">elements for Camera, Progress, Temperatures, and the AMS card.Add explicit IDs to the main cards
(e.g., id="card-camera", id="card-progress", id="card-motion").Wrap the Print Settings: Group the Temperatures, Print Speed, and Fan cards inside a new wrapper so they act as a single column block in the grid:
Introduce a specific grid-template-areas map for screens wider than 1100px to create the layout, placing the progress bar across the top:
Remove the max-height: 320px constraint from .cam-wrap and .cam-wrap img in the stylesheet, and give it a larger min-height (e.g., 550px) so the camera can stretch vertically to fill its massive new dedicated left-column area.
I have attached a modified index.html to this issue as a working example. Please note that this is just a quick proof of concept and not a perfect, final implementation!
There are still some minor layout quirks at specific intermediate resolutions (for example, the camera card temporarily jumps to the top right just before the screen narrows enough to trigger the mobile layout fallback or the progress bar at the top could be even smaller). It will definitely need some fine-tuning, but the attached file should give a great feel about what I mean.
index.html