plesty-server 0.3.2__tar.gz → 0.4.0.dev1__tar.gz

{plesty_server-0.3.2 → plesty_server-0.4.0.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: plesty-server
-Version: 0.3.2
+Version: 0.4.0.dev1
 Summary: The PLESTY bench application: installs, runs and field-tests device servers.
 Project-URL: Homepage, https://gitlab.com/plesty/core/plesty-bench
 Project-URL: Documentation, https://plesty.gitlab.io/core/plesty-bench/
@@ -11,34 +11,36 @@ License-File: LICENSE
 License-File: LICENSES/LGPL-3.0-or-later.txt
 Requires-Python: >=3.12
 Requires-Dist: click>=8.1
-Requires-Dist: plesty-bench==0.3.2
-Requires-Dist: plesty-lib>=0.4.0
+Requires-Dist: plesty-bench==0.4.0.dev1
+Requires-Dist: plesty-lib[report]>=0.5.0.dev8
 Requires-Dist: pyyaml>=6.0
 Requires-Dist: pyzmq>=26
 Provides-Extra: gui
-Requires-Dist: plesty-lib[gui]>=0.4.0; extra == 'gui'
+Requires-Dist: plesty-lib[gui]>=0.5.0.dev8; extra == 'gui'
 Requires-Dist: pyside6==6.11.2; extra == 'gui'
 Description-Content-Type: text/markdown
 
 # plesty-server · plesty-bench
 
-**The bench PC's own console for the PLESTY platform.** It installs hub device
-modules, starts and supervises their device servers, runs field tests against
-the real instruments and keeps the logs — so a lab bench is set up and kept
-running from one place instead of one venv, one terminal and one hand-written
-`uv` pin per instrument.
+**The bench PC's own console for the PLESTY platform.** It installs hub
+modules, starts and supervises device servers, runs field tests against the
+real instruments, and runs experiments across the lab's benches — keeping the
+logs, the runs and their reports — so a lab bench is set up and kept running
+from one place instead of one venv, one terminal and one hand-written `uv` pin
+per instrument.
 
 This repository publishes two packages:
 
 | | Install on | Install with |
 |---|---|---|
-| **`plesty-server`** — the bench application: CLI, Qt console, agent | the bench PC | `uv tool install "plesty-server[gui]"` |
+| **`plesty-server`** — the bench application: CLI, Qt console, agent | the bench PC | the installer from the [releases](https://gitlab.com/plesty/core/plesty-bench/-/releases) |
 | **`plesty-bench`** — the client that drives a bench from elsewhere | your own machine | `uv tool install plesty-bench` |
 
-On a Windows bench, the [releases](https://gitlab.com/plesty/core/plesty-bench/-/releases)
-carry a `setup.exe` (per-user, no admin); macOS and Linux have `install.sh`.
-Both install `uv`, run the command above and add a Start-menu / Launchpad
-entry — they contain no application code of their own.
+Each release carries a Windows `setup.exe` (per-user, no admin) and an
+`install.sh` for macOS and Linux. Both install the whole application,
+console included, pinned to that release, and add a Start-menu or Launchpad
+entry. Without an installer, `uv tool install "plesty-server[gui]"` installs
+the same thing on macOS or Linux.
 
 ## Bringing up a bench
 
@@ -68,25 +70,20 @@ plesty-bench -b lab-bench-03 control pm100d          # a control panel per devic
 ## Documentation
 
 **[Full documentation](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/index.md)**
-— start there if anything below is unfamiliar. It is in two parts.
+— start there if anything below is unfamiliar. It is in three parts:
 
-*Using a bench*, in the order you meet it:
-
-| | |
+| Part | Covers |
 |---|---|
-| [Setting up a bench](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/bench_setup.md) | The fleet file, declaring devices, ports, the `.env` |
-| [Device modules](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/modules.md) | The catalogue, installing, several versions side by side |
-| [Running device servers](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/running.md) | Start, stop, status, logs, the working fleet, headless benches |
-| [Field tests](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/field_test.md) | Running a module's field test against the instrument |
-| [The console](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/console.md) | Every part of the window, and the control panels |
-| [Working remotely](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/remote.md) | The agent and the `plesty-bench` client |
-| [Maintenance](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/maintenance.md) | Upgrading, clearing logs, purging, uninstalling |
-| [Command reference](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/cli.md) | Every `plesty-server` command |
+| [GUI](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/gui/index.md) | The window element by element: the Devices and Experiments tabs, every menu, every dialog, the Control window |
+| [CLI](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/cli/index.md) | `plesty-server`, `plesty-bench`, and every file and setting |
+| [Usages](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/usage/index.md) | Tasks start to finish: set up a bench, install modules, field-test, run an experiment, work remotely, run without a window, maintain |
+
+A new bench starts at [Set up a bench](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/usage/first_bench.md).
 
 *[Design and internals](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/design/index.md)*
-is the other part: the architecture, the process model, the port rules, the
-installer, the agent protocol, the platform differences and the release
-machinery — for contributors, and for anyone debugging behaviour that only
+covers the architecture, the process model, the port rules, the
+installer, the agent protocol, experiment runs, the platform differences and
+the release machinery — for contributors, and for anyone debugging behaviour that only
 makes sense once the mechanism is visible.
 
 New to the platform? The [PLESTY quickstart](https://plesty.net/learn/quickstart/index.html)

plesty_server-0.4.0.dev1/README.md

@@ -0,0 +1,68 @@
+# plesty-server · plesty-bench
+
+**The bench PC's own console for the PLESTY platform.** It installs hub
+modules, starts and supervises device servers, runs field tests against the
+real instruments, and runs experiments across the lab's benches — keeping the
+logs, the runs and their reports — so a lab bench is set up and kept running
+from one place instead of one venv, one terminal and one hand-written `uv` pin
+per instrument.
+
+This repository publishes two packages:
+
+| | Install on | Install with |
+|---|---|---|
+| **`plesty-server`** — the bench application: CLI, Qt console, agent | the bench PC | the installer from the [releases](https://gitlab.com/plesty/core/plesty-bench/-/releases) |
+| **`plesty-bench`** — the client that drives a bench from elsewhere | your own machine | `uv tool install plesty-bench` |
+
+Each release carries a Windows `setup.exe` (per-user, no admin) and an
+`install.sh` for macOS and Linux. Both install the whole application,
+console included, pinned to that release, and add a Start-menu or Launchpad
+entry. Without an installer, `uv tool install "plesty-server[gui]"` installs
+the same thing on macOS or Linux.
+
+## Bringing up a bench
+
+```bash
+plesty-server fleet init                      # a fleet.yaml to declare into
+plesty-server declare pm100d plesty-pm100d --version 0.2.1 \
+    --arg --address --arg "USB0::0x1313::…::INSTR"
+plesty-server start pm100d                    # installs, launches, waits until it answers
+plesty-server status
+```
+
+The instrument is now reachable from an experiment PC at this machine's
+address on the port `status` reports. `plesty-server gui` opens the same bench
+in a window; `plesty-server fleet run` keeps it up headless after a reboot.
+
+## Driving it from your own machine
+
+The bench serves an agent; the client sends it `plesty-server` command lines
+and follows the output.
+
+```bash
+plesty-bench -b lab-bench-03 status
+plesty-bench -b lab-bench-03 field-test pm100d --gates connect,drain
+plesty-bench -b lab-bench-03 control pm100d          # a control panel per device
+```
+
+## Documentation
+
+**[Full documentation](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/index.md)**
+— start there if anything below is unfamiliar. It is in three parts:
+
+| Part | Covers |
+|---|---|
+| [GUI](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/gui/index.md) | The window element by element: the Devices and Experiments tabs, every menu, every dialog, the Control window |
+| [CLI](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/cli/index.md) | `plesty-server`, `plesty-bench`, and every file and setting |
+| [Usages](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/usage/index.md) | Tasks start to finish: set up a bench, install modules, field-test, run an experiment, work remotely, run without a window, maintain |
+
+A new bench starts at [Set up a bench](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/usage/first_bench.md).
+
+*[Design and internals](https://gitlab.com/plesty/core/plesty-bench/-/blob/main/docs/design/index.md)*
+covers the architecture, the process model, the port rules, the
+installer, the agent protocol, experiment runs, the platform differences and
+the release machinery — for contributors, and for anyone debugging behaviour that only
+makes sense once the mechanism is visible.
+
+New to the platform? The [PLESTY quickstart](https://plesty.net/learn/quickstart/index.html)
+runs a whole experiment against a bench and is the gentlest way in.

{plesty_server-0.3.2 → plesty_server-0.4.0.dev1}/plesty/server/assets/console.qss

@@ -88,15 +88,23 @@ QMenu::separator {
   font-size: 11px;
 }
 
-QTableWidget, QTableView {
+/* Trees are styled with tables, not left out of them: an unstyled view keeps
+   Qt's own palette, whose alternate row is a pale grey that reads as disabled
+   text on this ground — and every other row of the Data tree was unreadable. */
+QTableWidget, QTableView, QTreeWidget, QTreeView {
   background: {{surface}};
   alternate-background-color: {{surface2}};
+  color: {{text}};
   border: none;
   gridline-color: {{line}};
   selection-background-color: {{selection}};
   selection-color: {{text_bright}};
 }
 
+QTreeWidget::branch {
+  background: transparent;
+}
+
 QHeaderView::section {
   background: {{surface2}};
   color: {{muted}};
@@ -108,7 +116,7 @@ QHeaderView::section {
   letter-spacing: 0.04em;
 }
 
-QTableWidget::item {
+QTableWidget::item, QTreeWidget::item {
   padding: 4px 8px;
 }
 
@@ -120,8 +128,12 @@ QTableWidget::item {
    like nothing is picked. */
 QTableWidget::item:selected,
 QTableView::item:selected,
+QTreeWidget::item:selected,
+QTreeView::item:selected,
 QTableWidget::item:selected:!active,
-QTableView::item:selected:!active {
+QTableView::item:selected:!active,
+QTreeWidget::item:selected:!active,
+QTreeView::item:selected:!active {
   background: {{selection}};
   color: {{text_bright}};
 }
@@ -157,6 +169,14 @@ QTabWidget::pane {
   background: transparent;
 }
 
+/* The strip the tabs sit on, which is not the tabs themselves. Without this it
+ * takes {{night}} from the QWidget rule and reads as a black band across a
+ * card that is {{surface}} — the tabs were already transparent, so what showed
+ * through was the wrong colour rather than the card behind them. */
+QTabBar {
+  background: transparent;
+}
+
 QTabBar::tab {
   background: transparent;
   color: {{muted}};
@@ -234,18 +254,29 @@ QPushButton#primary:disabled, QPushButton#danger:disabled {
   color: {{faint}};
 }
 
-QLineEdit, QComboBox, QSpinBox, QPlainTextEdit#editor {
+/* QAbstractSpinBox, not QSpinBox: a stylesheet selector names an exact class
+   and does not follow inheritance, so naming only QSpinBox left every float
+   field — QDoubleSpinBox — with Qt's own white-on-white default. */
+QLineEdit, QComboBox, QAbstractSpinBox, QPlainTextEdit#editor {
   background: {{surface2}};
+  color: {{text}};
   border: 1px solid {{line_strong}};
   border-radius: 6px;
   padding: 4px 8px;
   selection-background-color: {{selection}};
+  selection-color: {{text_bright}};
 }
 
-QLineEdit:focus, QComboBox:focus, QSpinBox:focus {
+QLineEdit:focus, QComboBox:focus, QAbstractSpinBox:focus {
   border-color: {{cyan}};
 }
 
+QAbstractSpinBox::up-button, QAbstractSpinBox::down-button {
+  background: {{surface}};
+  border-left: 1px solid {{line}};
+  width: 14px;
+}
+
 QComboBox QAbstractItemView {
   background: {{surface2}};
   border: 1px solid {{line_strong}};
@@ -303,6 +334,64 @@ QGroupBox::title {
   font-weight: 600;
 }
 
+/* A group of an experiment's settings, or one device of its fleet file. The
+   title is what the eye finds first — accent colour, heavier than any key —
+   and the keys under it are muted, so the values are what reads brightest. */
+QGroupBox#settingsGroup {
+  background: {{surface}};
+  border: 1px solid {{line}};
+  border-radius: 8px;
+  margin-top: 20px;
+  padding: 14px 12px 10px 12px;
+}
+
+QGroupBox#settingsGroup::title {
+  subcontrol-origin: margin;
+  left: 12px;
+  padding: 0 6px;
+  color: {{cyan}};
+  font-size: 13px;
+  font-weight: 700;
+  letter-spacing: 0.03em;
+}
+
+QLabel#settingKey {
+  background: transparent;
+  color: {{muted}};
+}
+
+/* A value shown, not set here — an address built from a machine and a port.
+   Flat and muted, so it does not read as a field waiting for input. */
+QGroupBox#settingsGroup QLineEdit[readOnly="true"] {
+  background: transparent;
+  border-color: transparent;
+  color: {{muted}};
+}
+
+/* Every QWidget is painted the window's colour; inside a group box that drew a
+   dark strip behind a check box, the width of the row. What is not an input
+   takes the box's colour instead. */
+QGroupBox#settingsGroup QCheckBox,
+QGroupBox#settingsGroup QLabel,
+QWidget#listEditor {
+  background: transparent;
+}
+
+/* The column names over a list setting's rows. */
+QLabel#listHeading {
+  background: transparent;
+  color: {{faint}};
+  font-size: 11px;
+}
+
+/* + and − at the end of each row of a list setting. */
+QPushButton#listButton {
+  min-width: 24px;
+  max-width: 24px;
+  padding: 2px 0;
+  font-weight: 700;
+}
+
 QStatusBar {
   background: {{night2}};
   border-top: 1px solid {{line}};