Panel Consoles
The same three subjects as the rest of this section — charting, layout & data, documents —
rebuilt out of magx-panel elements rather than bespoke markup. Not because panels
draw a better dashboard, but because a draggable panel surface is a different kind of interface: an operator console, where the controls and the readouts live in the
same movable containers and the operator decides the arrangement.
Every control below routes through the single documented integration point — one magx-panelValueChanged listener on document, switched on element id.
Three consoles, one handler, no per-element subscription API. Drag any title bar to rearrange;
double-click it to collapse. The data is synthetic and regenerates from the Reshuffle button in
the GPU console.
Animation is off until you press play, because a console that moves while you are reading it is
harder to read. Every chart below shares this one clock: the sparklines slide, the readouts
drift, and the fleet table re-sorts, all from the same frame counter. Reshuffle
reseeds the generators instead of advancing them, so you get a different plausible situation
rather than the next second of this one.
Telemetry on the left, actuators on the right — the arrangement every device console converges
on, because a control you cannot see the effect of is a control you do not trust. Power limit and
fan speed feed the temperature model directly, so moving a slider moves the readout. Apply is a countdown-mode button — it arms for three seconds and commits when it elapses, which
is the cheapest way to make an expensive command cost more than a stray click. Reset is a plain
momentary button and pushes its defaults back into the sliders rather than only into state.
The FPS range and the Reshuffle button are the same two controls the rest of the Interface section carries in its own strip — here they are panel elements instead, which is the whole comparison.
A table inside a panel is the case where this composition strains: panels are narrow by design, and a table wants width. The honest answer is to make the rows narrow too — host, one bar, one state chip — and put the filters in their own panel rather than as a toolbar above the data. What is gained is that the filter panel can be dragged away entirely once it has been set.
The strongest case for panels. A processing pipeline has a natural panel-per-stage decomposition, the settings genuinely are separate from the queue, and the operator wants the extracted-text pane large and everything else small — which is exactly what dragging and collapsing give them. Press Process to run the stages; the OCR toggle changes both the pipeline labels and the confidence figures, because switching to an embedded text layer is a different job.
ENGINE glm-ocr · 0.9B MODE raster → text PAGES 14 BYTES 656 KB CONF 89.6% IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF NEW YORK Plaintiff having moved for an order compelling production of the documents identified in Exhibit C, and the Court having considered the submissions of the parties …