@synopackageland/ui 0.17.10 → 0.17.11

package/docs/layout-rules.md

@@ -40,9 +40,13 @@ These rules keep pages built from `@synopackageland/ui` consistent. The componen
 - Colours are fixed by role: section title `--ui-text` semibold 14px, label and value `--ui-text`, help text `--ui-text-secondary` 12px.
 - A `SettingsRow` with a `description` aligns its label with the control's first line, not the middle of control and description.
 - A row that is only a button: give it a `SettingsRow` label when it acts on one thing, or put it in the section `#footer`. Inside a horizontal form, use `FormActions inset` so the button starts on the value edge.
-- A DSM-native settings page reads its structure from indentation and spacing. Each section is a `Fieldset` (blue title over a dashed divider, collapsible); sections one after another keep a 20px gap. Fields are a `Form` with one `labelWidth` (or the theme's column) and `FormItem`s.
-- Options that only matter while a checkbox or switch is on go in a `FormGroup` right after it, with `:disabled="!on"`: one 28px indent, every control inside disabled and dimmed, and the labels inside give up the indent so the controls stay on the form's column. Nest a `FormGroup` for a second level. Do not indent with your own padding or disable each child by hand.
-- Explanation is a short `description` under its field. A note the user should read before changing a section is a `FormNote` (DSM's teal "Note:" with bullets) after the fields; facts to read or copy (addresses, paths) go in an `InfoBox`. A warning or an error is a `Callout`. Do not write long full-width paragraphs between fields.
+- A DSM-native settings page reads its structure from indentation and spacing (Control Panel > Network > General). Each section is a `Fieldset`: a blue title with a chevron (up while open) over a dashed divider across the whole width, collapsible. Sections one after another keep a 20px gap. A one-line explanation of the section is the Fieldset's `description`, directly under the title and across the whole width, not in the label column. Fields are one `Form` with one `labelWidth` (or the theme's column) and `FormItem`s; one `Form` may hold several Fieldsets.
+- A read-only value is a `FormItem` with `text-only`: plain text in the control column, level with its label. A button that acts on it (Edit) goes in the item's `#after` slot and follows the field column.
+- Options that only matter while a checkbox or switch is on go in a `FormGroup` right after it, with `:disabled="!on"`. The parent is a `FormItem :label="false"`, so it starts at the section's left edge. The group indents one 28px step, disables and dims every control inside, and the labels inside give up the indent so the controls stay on the form's column, as DSM draws them. Nest a `FormGroup` for a second level. Do not indent with your own padding or disable each child by hand.
+- A section button such as Advanced Settings goes inside the `FormGroup` it belongs to, after its fields, as a plain `Button`: it starts on the group's indent and follows the group's disabled state. Do not centre it or put it in the label column.
+- A unit goes in the `Input`'s `unit` (or `#unit` slot): `<Input v-model="timeout" type="number" unit="s" />` puts "s" right after the field. Do not put units in the FormItem's `#after` slot, which starts after the whole field column.
+- Explanation is a short `description` under its field. A note is a `FormNote`: one remark reads "Note: …" on one line, two or more `items` become a list under the heading. Put it under the field it is about with `inset` (it starts on the field column), or at the end of the section without. Facts to read or copy (addresses, paths) go in an `InfoBox`. A warning or an error is a `Callout`. Do not write long full-width paragraphs or a separate "Note:" heading between fields.
+- A settings page has one Apply. On a page or window, put Reset then Apply in the footer (`Footbar`, `AppActionBar`), as Control Panel does; inside a form that ends the page, use `FormActions inset`. Do not put a Save between the fields of a section.
 
 ## Tables
 

package/docs/theme-hooks.md

@@ -94,8 +94,10 @@ here stay implementation details and can change in any release.
 | `data-ui-stat-tile-label`, `-value`, `-unit`, `-note` | `StatTile` parts | present |
 | `data-ui-stat-tile-group` | `StatTileGroup` | present |
 | `data-ui-fieldset` | `Fieldset` | present |
+| `data-fieldset-description` | `Fieldset` description under the title | present |
 | `data-ui-form-group` | `FormGroup` (`data-disabled` while disabled) | present |
-| `data-ui-form-note`, `data-ui-form-note-title` | `FormNote` and its heading | present |
+| `data-ui-form-note`, `data-ui-form-note-title` | `FormNote` and its heading (`data-inset` with `inset`) | present |
+| `data-ui-input-unit` | `Input` unit after the field | present |
 | `data-ui-info-box`, `data-ui-info-box-title` | `InfoBox` and its title | present |
 | `data-ui-stacked-bar`, `-track`, `-segment`, `-legend`, `-remainder` | `StackedBar` parts (a segment has `data-key` and `data-tone`) | present |
 | `data-ui-section-tabs-row`, `data-ui-section-tabs-actions` | `SectionTabs` with `#actions`: the row and the actions | present |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synopackageland/ui",
-  "version": "0.17.10",
+  "version": "0.17.11",
   "description": "Shared Vue 3 UI component library with a DSM 7 inspired application theme",
   "license": "MIT",
   "type": "module",