@smartbit4all/ng-client 7.3.5 → 7.3.6

package/MIGRATION-7.0.md

@@ -2143,7 +2143,7 @@ Additive: a host without a keymap gets one binding, Escape closes a dialog that
 - **New in the public API:** model `Keybinding`, `View.keybindings`,
   `ComponentModel.keybindings`; Java `KeyChord`, `KeyboardKeys`, `KeybindingSettingApi`.
 
-### New in 7.3.3: a stored layout names its HTML template by key (#30388)
+### New in 7.3.5: a stored layout names its HTML template by key (#30388)
 
 Additive, and needs the matching platform. Nothing changes for a layout that names no key.
 

package/WIDGETS.md

@@ -159,6 +159,34 @@ An action trigger (`data-sb4-action`) looks its action up in the same list, and
 (`data-sb4-icon`, `data-sb4-icon-key`) hydrates into a `smart-icon` the same way. See
 `HTML-WIDGET.md`.
 
+**A toolbar can be drawn as tabs.** How it draws its actions is the `appearance` of its
+`[toolbarPropertes]` (`ToolbarAppearance`: `BUTTONS`, the default, or `TABS`), next to `direction`,
+`alignment` and `scrollable`. A backend layout sends it in the toolbar's properties; a template
+sets it the same way:
+
+```html
+<smart-ui-action-toolbar [id]="toolbarId" [toolbarPropertes]="{ appearance: 'TABS' }">
+</smart-ui-action-toolbar>
+```
+
+A `TABS` toolbar draws every action that takes part in view-activation (`viewActivated` is not
+`null`) as a tab and the activated one as the selected tab; any other action stays the button it
+would be, in the same row. The row gets the class `sb4-tabs` and the role `tablist`, a tab the
+class `sb4-tab`, the role `tab` and `aria-selected`, on top of the `sb4-view-opener` /
+`sb4-view-activated` classes it had anyway — so the selected tab is
+`button.sb4-tab.sb4-view-activated`. An action with a `rowState` gets, as a tab, the class of a
+grid row in that state (`sm-grid-row-new`, `-modified`, `-deleted`).
+
+The row follows `direction`: a horizontal one marks the selected tab on its bottom edge and
+scrolls with the arrow buttons when `scrollable`; a vertical one marks it on the edge facing the
+content, ignores `scrollable` and scrolls natively, so its holder has to give it a height. Restyle
+through the `--sb4-tab-*` custom properties (`-color`, `-selected-color`, `-indicator-color`,
+`-indicator-width`, `-bg`, `-selected-bg`, `-hover-bg`, `-font-weight`, `-selected-font-weight`,
+`-gap`, `-row-border-color`), set on any element around the toolbar. The tab look lives in the
+toolbar's stylesheet: a `ui-action-button` with `[tab]="true"` outside a `TABS` toolbar gets the
+role and the class but not the look. Which action is a tab, and which one is selected, is the
+backend's to say — a widget never sets `viewActivated`.
+
 **A `UiActionModel` is frozen.** Every field is `readonly`, and `[uiActionModels]` takes
 `readonly UiActionModel[]`. Build a new entry; never edit one. Writing into an entry a
 toolbar is already rendering never reached the screen under zone.js either — it only appeared