@gemboss/ui 0.51.0 → 0.53.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +59 -0
- package/README.md +67 -55
- package/catalog/editor.html +1 -1
- package/catalog/index.html +503 -219
- package/gemboss-ui.css +1 -1
- package/package.json +1 -1
- package/parts/components.css +1 -1
- package/parts/core.css +1 -1
- package/parts/shell.css +1 -1
- package/src/assistant/engine-settings-store.ts +95 -0
- package/src/assistant/engine-settings.tsx +106 -0
- package/src/assistant/engine.tsx +101 -324
- package/src/assistant/index.ts +4 -1
- package/src/assistant-engine.css +1 -1
- package/src/dialog.tsx +34 -5
- package/src/editor/picker-grid.tsx +5 -2
- package/src/editor/picker.tsx +5 -2
- package/src/editor/popover.tsx +2 -1
- package/src/engine-plain.js +1 -1
- package/src/escape.ts +16 -0
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,53 @@ Versions up to 0.9.0 are described in the README, each in the section that intro
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## 0.53.0 (25/10/2026)
|
|
8
|
+
|
|
9
|
+
**The engine chip's popup is gone: Settings › AI & engines is the only place the engine is chosen** (Chris's condition for the
|
|
10
|
+
0.52.0 `engine-plain.js` ceiling, 24/10/2026: "gỡ chế độ popup khi mọi bề mặt đã chuyển"). Every surface on the kit moved to
|
|
11
|
+
Settings in 0.52.0 (partner-radar, content-radar, search-radar, talent-radar, gemwatcher, GemFeedback, gemfactory, gemcare, and the
|
|
12
|
+
admin), so the 0.25 popup had no reader left. Checked 25/10: gemfactory's builder has no engine chip (its chat runs on the
|
|
13
|
+
server only, no bridge), and gemcommunity, gemplugin and gemform draw none.
|
|
14
|
+
|
|
15
|
+
Removed (breaking)
|
|
16
|
+
- `EnginePanel`, and the chip's popup with it: the top-layer dialog, its tabs, its Escape handling and its placement.
|
|
17
|
+
- `EnginePicker` props `open`, `tab`, `onTabChange`, `end`; `onOpenSettings` is now REQUIRED (on `useEnginePicker` too). Labels
|
|
18
|
+
`dialog`, `tabs`, `engineTab`, `setupTab`, `statusTab`, `updateDue`, `close`.
|
|
19
|
+
- `engine-plain.js`: the popup, its tabs, Escape and placement. Without `onOpenSettings` the chip logs a `console.error` and
|
|
20
|
+
opens nothing. `picker.close()` stays and does nothing (as `useEnginePicker().close()` since 0.52.0).
|
|
21
|
+
- CSS: `.gb-engine-panel`, `.gb-engine-tabs`, `.gb-engine-pane` and their rules; `.gb-engine-cmd` no longer caps its height
|
|
22
|
+
(that was the popup's 360px). A surface rule scoped to `.gb-engine-panel` no longer matches: scope it to `.gb-engine-settings`.
|
|
23
|
+
- `EngineSettings` / `EngineSettingsSection` no longer require `onOpenSettings` (`EngineCardProps`): the cards never call it.
|
|
24
|
+
|
|
25
|
+
Fixed
|
|
26
|
+
- The pairing code (`.gb-engine-code code`) resets a surface's own `code` look, as the command already did: content-radar tinted
|
|
27
|
+
it as an inline-code pill in Settings (its exemption named `.gb-engine-panel`).
|
|
28
|
+
- The chip asked the section to focus twice per click (its own request, then `openTab`'s): `openTab` alone asks now.
|
|
29
|
+
- `engine-plain.js` Settings section: a poll that changed the bridge between running and outdated (the callout above Install or
|
|
30
|
+
update came or went) tore the setup block out and put a new one back, so a pairing-code field in `setup.steps` lost its focus
|
|
31
|
+
mid-typing (0.52.0). A keyed block that only shifted now stays in place.
|
|
32
|
+
|
|
33
|
+
Weight: `engine-plain.js` 4979 B gzip, ceiling 6723 → 5491 B (under 0.51's 5959).
|
|
34
|
+
|
|
35
|
+
## 0.52.0 (25/10/2026)
|
|
36
|
+
|
|
37
|
+
**The assistant's engine in Settings › AI & engines; the composer chip opens it** (24/10/2026, Chris: "đưa hết về nằm trong
|
|
38
|
+
popup settings để có nhiều không gian hơn… bấm vào đó mở settings"). The chip's 0.25 popup was 360px wide and 212–405px tall over
|
|
39
|
+
the chat (measured on five surfaces), with the bridge split over two more tabs. The admin's top-bar AI chip already opened
|
|
40
|
+
Settings › AI & engines: now every assistant does that.
|
|
41
|
+
|
|
42
|
+
Added
|
|
43
|
+
- `EnginePicker` `onOpenSettings(tab)` and `useEnginePicker({ onOpenSettings })`: the chip opens the surface's Settings, no
|
|
44
|
+
popup. `openTab("setup")` opens it with Install or update in view and focus on Copy; `open` is true while the section is SEEN
|
|
45
|
+
(not mounted: a closed SettingsDialog keeps its section); `close()` does nothing.
|
|
46
|
+
- `EngineSettings` and `EngineSettingsSection` (`@gemboss/ui/assistant`): the three tabs as two cards, Engine (engines, models,
|
|
47
|
+
effort, notes, problem) and Bridge on your machine (the callout, State / Version / Starts at sign-in, the actions, Install or
|
|
48
|
+
update). The section draws what the assistant's chip published (a module store, engine-settings-store.ts), so a surface puts
|
|
49
|
+
`<EngineSettingsSection />` in its Settings and changes nothing else. Labels `state`, `setupTitle`.
|
|
50
|
+
- `engine-plain.js`: `onOpenSettings`, `picker.mountSettings(el)`, `picker.unmountSettings()`, the same markup.
|
|
51
|
+
|
|
52
|
+
Weight: `engine-plain.js` ceiling 5959 → 6723 B gzip (Chris's OK, 24/10/2026): the popup mode goes once every surface has moved.
|
|
53
|
+
|
|
7
54
|
## 0.51.0 (24/10/2026)
|
|
8
55
|
|
|
9
56
|
**AuthSignIn: the server's sentence, a notice, the cursor, and a sentence that blames no field** (24/10/2026). Moving the
|
|
@@ -84,6 +131,18 @@ Added
|
|
|
84
131
|
- `auth-standard-browser.test.ts` in Chromium (1280 x 800 and 390 x 844, light and dark), each layout claim beside a
|
|
85
132
|
negative control; the catalog's "Đăng nhập" section draws the standard sign-in (light and dark) and two sign-up steps.
|
|
86
133
|
|
|
134
|
+
**`Dialog` gives the focus back to a clicked opener that dropped it** (24/10/2026). Polaris' buttons blur themselves on mouseup, so
|
|
135
|
+
a popup opened by a click on one found `<body>` focused and gave the focus back to `<body>` on Escape or ✕ (the catalogue picker's
|
|
136
|
+
Change, measured). When the focus is on `<body>` as it opens, the opener is the control the last press landed on (in the last 2 s,
|
|
137
|
+
still in the page); an opener that kept its focus is unchanged.
|
|
138
|
+
Also: `onClose`'s updates are applied (`flushSync`) before the focus goes back, so a close that replaces its opener (a picker's
|
|
139
|
+
typed handle saved as it closes) hands the focus to what replaced it, not to the button an instant before it left; and `Dialog`
|
|
140
|
+
takes `returnFocusTo` (useModalDialog's selector, for an opener gone by then).
|
|
141
|
+
Its Escape is its own: the browser closes the `<dialog>` and neither the keydown nor the keyup goes further out. A Polaris Modal it
|
|
142
|
+
was opened from closes on the Escape KEYUP (its keydown only marks it closing), so stopping the keydown was not enough. One helper,
|
|
143
|
+
`consumeEscape` (escape.ts), does both for every kit part that acts on Escape: Dialog, PickerList's and PickerGrid's box (clearing
|
|
144
|
+
its words), Popover (back or close).
|
|
145
|
+
|
|
87
146
|
**The public site layer is deprecated** (24/10/2026). Public websites use `@gemboss/website-ui` (gemboss-www
|
|
88
147
|
[packages/website-ui](https://github.com/chriskoh26/gemboss-www/tree/main/packages/website-ui), on npm), the full site kit with its rules and CLI; Chris chose one kit for every GemCommerce
|
|
89
148
|
website. `SiteHeader`, `SiteBrand` and `site.css` stay, unchanged, until news.gemboss.ai and the community home move;
|
package/README.md
CHANGED
|
@@ -72,7 +72,7 @@ its CSS out of the build with it (`sideEffects`). gzip of the minified file, as
|
|
|
72
72
|
| editor-tiles | `@gemboss/ui/editor-tiles.css` | `packages/ui/src/editor-tiles.css` | `ChoiceTiles`: a closed choice of shapes as picture tiles | 0.5 KB | `ChoiceTiles` imports it |
|
|
73
73
|
| editor-insert | `@gemboss/ui/editor-insert.css` | `packages/ui/src/editor-insert.css` | the page editor's insert menu (the + on a picked element) | 0.6 KB | admin `InsertElementMenu` imports it |
|
|
74
74
|
| reactions | `@gemboss/ui/reactions.css` | `packages/ui/src/reactions.css` | the emoji reactions and their picker | 0.8 KB | `Reactions` / `ReactionPicker` import it |
|
|
75
|
-
| assistant-engine | `@gemboss/ui/assistant-engine.css` | `packages/ui/src/assistant-engine.css` | the engine picker (chip +
|
|
75
|
+
| assistant-engine | `@gemboss/ui/assistant-engine.css` | `packages/ui/src/assistant-engine.css` | the engine picker (chip + Settings › AI & engines) and the bridge notice | 1.9 KB | `EnginePicker` / `EngineSettings` / `BridgeNotice` import it |
|
|
76
76
|
| chat | `@gemboss/ui/chat.css` + `chat-composer.css` | `packages/ui/src/chat.css`, `packages/ui/src/chat-composer.css` | the chat body, the composer | 3.0 + 0.9 KB | the chat components (0.29.0); a page writing the markup links them |
|
|
77
77
|
| assistant-chat | `@gemboss/ui/assistant-chat.css` | `packages/ui/src/assistant-chat.css` | the chat pieces the package draws (0.29.0): column, starters that wrap, meta, errors, notes, paperclip | 0.9 KB | `AssistantChat` and its pieces import it |
|
|
78
78
|
| minichart | `@gemboss/ui/minichart.css` | `packages/ui/src/minichart.css` | `Sparkline`, `ShareBar` (0.30.0) | 0.5 KB | those components import it |
|
|
@@ -447,16 +447,20 @@ the menu, rename, pin, delete, collapse, an empty list) and the framed layout to
|
|
|
447
447
|
</script>
|
|
448
448
|
```
|
|
449
449
|
|
|
450
|
-
## The engine picker (0.25.0)
|
|
450
|
+
## The engine picker: `EnginePicker` (0.25.0), Settings › AI & engines (0.52.0), `BridgeNotice`
|
|
451
451
|
|
|
452
452
|
Which engine answers the assistant, and the bridge on the user's machine, without spending the chat's space on it
|
|
453
453
|
(Chris 07/10/2026: content-radar's assistant spent close to half its frame on an ENGINE / MODEL / EFFORT row, an
|
|
454
|
-
"outdated bridge" block and the install command).
|
|
454
|
+
"outdated bridge" block and the install command). A chip in the composer row says the engine; the choice itself lives in
|
|
455
|
+
the surface's Settings, in an "AI & engines" section (Chris 24/10/2026: "đưa hết về nằm trong popup settings để có nhiều
|
|
456
|
+
không gian hơn"). That is the admin's shape: its top-bar "AI: GemBoss AI" opens Settings › AI & engines. Until 0.52.0 the
|
|
457
|
+
chip opened a 360px popup with three tabs; 0.53.0 removed it.
|
|
455
458
|
|
|
456
459
|
```tsx
|
|
457
|
-
import { EnginePicker,
|
|
460
|
+
import { BridgeNotice, EnginePicker, EngineSettingsSection, useEnginePicker } from "@gemboss/ui/assistant"; // brings assistant-engine.css
|
|
458
461
|
|
|
459
|
-
|
|
462
|
+
// The chip: a door to the surface's Settings, opened on its AI & engines section.
|
|
463
|
+
const picker = useEnginePicker({ onOpenSettings: () => openSettings("ai") });
|
|
460
464
|
<EnginePicker {...picker.props}
|
|
461
465
|
engines={[{ id: "claude", label: "Claude Code", note: "Your Claude subscription" }, { id: "server", label: "Server" }]}
|
|
462
466
|
engine={engine} onEngineChange={setEngine}
|
|
@@ -466,47 +470,51 @@ const picker = useEnginePicker(); // open + tab, shared with the notice
|
|
|
466
470
|
setup={{ command: installCommand, pairingCode, note: "The panel reconnects in a few seconds." }}
|
|
467
471
|
statusActions={<button className="ui-btn" onClick={recheck}>Check again</button>} />
|
|
468
472
|
|
|
473
|
+
// In the surface's Settings (the kit's SettingsDialog: { id: "ai", label: "AI & engines", icon: "sparkle" }):
|
|
474
|
+
<EngineSettingsSection />
|
|
475
|
+
|
|
469
476
|
// Only when a turn FAILED because of the bridge, one line in the stream:
|
|
470
477
|
<BridgeNotice onOpenSetup={() => picker.openTab("setup")}>The bridge on your machine is not responding.</BridgeNotice>
|
|
471
478
|
```
|
|
472
479
|
|
|
473
480
|
- **Chip**: engine name, the model when it is not the default (`id: ""`), a dot for `bridge.state`: green `running`,
|
|
474
|
-
amber `outdated`, red `offline` / `unpaired`, hollow `checking`. Its accessible name says the state in words.
|
|
475
|
-
|
|
476
|
-
|
|
477
|
-
|
|
478
|
-
|
|
479
|
-
|
|
480
|
-
|
|
481
|
-
|
|
481
|
+
amber `outdated`, red `offline` / `unpaired`, hollow `checking`. Its accessible name says the state in words. A click
|
|
482
|
+
calls `onOpenSettings("engine")`; there is no popup and no `aria-expanded`. 28px under a mouse, 44px under a coarse
|
|
483
|
+
pointer.
|
|
484
|
+
- **The section**: `EngineSettingsSection` draws what the chip on the page was given (`engine-settings-store.ts`: the chip
|
|
485
|
+
publishes its props, the section reads them), so the surface hands its engine props to the chip only and changes
|
|
486
|
+
nothing else. Two cards, one under the other: **Engine** (the engines as radios, or each with its own models; model;
|
|
487
|
+
effort; `notes`) and **Bridge on your machine** (one callout for outdated / offline / unpaired, the State / Version /
|
|
488
|
+
Starts at sign-in rows, `statusActions`, then "Install or update": the steps, the command with Copy, the pairing code,
|
|
489
|
+
the note). With no chip on the page it says the assistant has not loaded yet (`empty` replaces that line).
|
|
490
|
+
`EngineSettings` takes the props itself, for a surface that holds them where its settings are drawn, and the catalog.
|
|
491
|
+
- **`picker.open`** is the section being SEEN (an IntersectionObserver), not mounted: the kit's SettingsDialog keeps its
|
|
492
|
+
sections mounted while it is closed, and a surface that probes the bridge while `picker.open` would poll for ever.
|
|
493
|
+
- **`picker.openTab("setup" | "status" | "engine")`** asks the section to scroll that part to the top and focus its first
|
|
494
|
+
control (Copy, for Install or update), then calls `onOpenSettings(tab)`. That is `BridgeNotice`'s Open setup.
|
|
495
|
+
- **Keys and picks**: ↑/↓ move between engines and pick (one Tab stop; one that cannot be picked is skipped). A pick
|
|
496
|
+
calls back at once and the chip follows; nothing closes Settings.
|
|
497
|
+
- **Not in the chat**: no standing warning, no command in the conversation. The amber dot on the chip is the warning.
|
|
498
|
+
`BridgeNotice` is for a turn that actually failed, once.
|
|
482
499
|
- **For the admin (0.29.0)**: `EngineChoice.mark` ("claude", "codex") is shown on the chip in place of the name when the
|
|
483
500
|
composer is too narrow (`ChatComposer` density icon); `EngineChoice.models` on every engine + `onPick(engine, model)`
|
|
484
|
-
lists each engine with its own models at once, and one click picks both
|
|
485
|
-
|
|
486
|
-
a switch is in flight.
|
|
501
|
+
lists each engine with its own models at once, and one click picks both; `problem` is a red line on the Engine card
|
|
502
|
+
("Wait for the current answer to finish"); `disabled` disables the chip while a switch is in flight.
|
|
487
503
|
- The picker itself knows no bridge: the surface hands in its state, the command and the callbacks. Since 0.32.0 the
|
|
488
|
-
surface usually gets all three from `useBridge` + `bridgePickerProps` (next section).
|
|
489
|
-
|
|
490
|
-
|
|
491
|
-
|
|
492
|
-
|
|
493
|
-
|
|
494
|
-
|
|
495
|
-
|
|
496
|
-
Tests: `packages/ui/src/assistant/engine.test.tsx` (markup, styles, its own entry), `packages/ui/src/assistant/engine-browser.test.tsx`
|
|
497
|
-
(Chromium: top layer through a clipping frame, keys, focus, copy, Open setup, 44px; with negative controls).
|
|
498
|
-
|
|
499
|
-
**Escape (0.27.0).** An Escape that closes the panel is marked handled (`preventDefault`) also when focus is outside it
|
|
500
|
-
(the composer): a surface whose own Escape hides the assistant and checks `defaultPrevented` leaves that key alone, and the
|
|
501
|
-
next Escape is its own again. Before, the key went on unmarked and React re-renders between the picker's listener and the
|
|
502
|
-
surface's, so each surface needed a window-capture marker to tell the two apart (gemlabs #922, gemfeedback #66). With
|
|
503
|
-
0.27.0 the surface's `!e.defaultPrevented` is enough.
|
|
504
|
+
surface usually gets all three from `useBridge` + `bridgePickerProps` (next section).
|
|
505
|
+
- **Gone in 0.53.0** with the popup: `EnginePanel`; the props `open`, `tab`, `onTabChange`, `end`; the labels `dialog`,
|
|
506
|
+
`tabs`, `engineTab`, `setupTab`, `statusTab`, `updateDue`, `close`. `picker.close()` stays and does nothing, so a Stop /
|
|
507
|
+
Remove handler written for the popup still runs; `picker.focusChip()` / `picker.chipRef` are unchanged.
|
|
508
|
+
|
|
509
|
+
Tests: `packages/ui/src/assistant/engine.test.tsx` (markup, styles, its own entry, and that the popup's classes are no
|
|
510
|
+
longer styled), `packages/ui/src/assistant/engine-settings-browser.test.tsx` (Chromium: the chip opens Settings, picks,
|
|
511
|
+
keys, Copy, Open setup lands on Install or update, seen vs mounted, 44px; with negative controls).
|
|
504
512
|
|
|
505
513
|
### Plain HTML: `gembossUI.enginePicker()` (0.27.0)
|
|
506
514
|
|
|
507
|
-
`engine-plain.js`, after `kit-plain.js`, for a page with no React (gemcare). The same markup and classes as
|
|
508
|
-
(asserted: same class set for the
|
|
509
|
-
|
|
515
|
+
`engine-plain.js`, after `kit-plain.js`, for a page with no React (gemcare, gemfactory). The same markup and classes as
|
|
516
|
+
the components (asserted: the same class set as `EnginePicker` for the chip and as `EngineSettings` for the section), so
|
|
517
|
+
`assistant-engine.css` draws it:
|
|
510
518
|
|
|
511
519
|
```html
|
|
512
520
|
<link rel="stylesheet" href="/ui/assistant-engine.css"> <!-- require.resolve("@gemboss/ui/assistant-engine.css") -->
|
|
@@ -521,31 +529,35 @@ const picker = gembossUI.enginePicker(document.querySelector(".gemboss-ec-toolba
|
|
|
521
529
|
models, model, onModelChange, efforts, effort, onEffortChange, effortDisabled, notes, modelControl,
|
|
522
530
|
bridge: { state: "outdated", version: "8", latest: "10", autostart: true, detail: "…" }, showBridgeDot: true,
|
|
523
531
|
setup: { command, pairingCode, steps, note }, statusActions: [checkAgainButton],
|
|
524
|
-
|
|
532
|
+
onOpenSettings: (tab) => openSettings("ai"), // required: the chip's click (no popup to fall back to)
|
|
533
|
+
onOpenChange, locked, labels,
|
|
525
534
|
});
|
|
535
|
+
// The surface's Settings, when it draws its AI & engines section:
|
|
536
|
+
picker.mountSettings(sectionElement); // two cards: Engine · Bridge on your machine (with Install or update)
|
|
537
|
+
picker.unmountSettings(); // when the section goes away
|
|
526
538
|
picker.update({ bridge: { state: "running" } }); // a poll: bridge / setup / labels merge one level; patched in place
|
|
527
|
-
picker.openTab("setup"); picker.
|
|
539
|
+
picker.openTab("setup"); picker.isOpen(); picker.destroy();
|
|
528
540
|
log.append(gembossUI.bridgeNotice({ text: "The bridge on your machine is not responding.", onOpenSetup: () => picker.openTab("setup") }));
|
|
529
541
|
```
|
|
530
542
|
|
|
531
543
|
Strings are text; `steps`, `notes`, `detail`, `statusActions` and `modelControl` may also be a Node, an array of Nodes or a
|
|
532
544
|
DocumentFragment: placed once and left where they are, so a field in them keeps focus, caret and events across redraws.
|
|
533
|
-
A redraw PATCHES the
|
|
534
|
-
or the model select stays, and a
|
|
535
|
-
|
|
536
|
-
|
|
537
|
-
|
|
538
|
-
|
|
539
|
-
`packages/ui/src/engine-plain.test.ts`
|
|
540
|
-
|
|
541
|
-
|
|
545
|
+
A redraw PATCHES the chip and the section in place (the same elements, only what changed, as React does): focus on an
|
|
546
|
+
engine row or the model select stays, and a keyed block that only shifted (the callout came or went above Install or
|
|
547
|
+
update) is kept, not torn out and put back (0.53.0: that blurred a pairing-code field on a poll). Behaviour is delegated
|
|
548
|
+
from the section (`data-*`). A pick from the engine list, the model or the effort updates the picker at once and calls back
|
|
549
|
+
(no callback: that row is disabled, as in the component); `update()` is how the page says anything else changed.
|
|
550
|
+
`isOpen()` is the section being seen, as in the component; `onOpenChange` says when that changes. Without
|
|
551
|
+
`onOpenSettings` the chip logs a `console.error` and opens nothing. Tests: `packages/ui/src/engine-plain.test.ts`
|
|
552
|
+
(Chromium: the components' class sets, picks, keys, Copy, redraws that keep focus and a caller's field without a blur or
|
|
553
|
+
change, merge rules, seen vs mounted, Open setup, 44px; each with its negative control).
|
|
542
554
|
|
|
543
555
|
## The bridge (0.32.0): `useBridge`, `createBridgeClient`, `bridgePickerProps`
|
|
544
556
|
|
|
545
557
|
The bridge is the small server a teammate installs on their machine so the assistant can run Claude Code / Codex on their
|
|
546
558
|
own subscription; the page talks to it at `http://127.0.0.1:<port>`, and the surface's server never sees that call.
|
|
547
559
|
content-radar, partner-radar and search-radar carried the same ~300 lines for it each (find it behind Chrome's Local Network
|
|
548
|
-
Access permission, pair, a data token, a turn and its stream, polls, "it went away", the
|
|
560
|
+
Access permission, pair, a data token, a turn and its stream, polls, "it went away", the setup and status of the bridge), and a
|
|
549
561
|
review fixed one copy at a time. Once, here:
|
|
550
562
|
|
|
551
563
|
```tsx
|
|
@@ -554,7 +566,7 @@ import { bridgePickerProps, bridgeControlNote, createBridgeClient, postTurn, rea
|
|
|
554
566
|
// Module level (one per page): its data token is cached on it.
|
|
555
567
|
const bridgeClient = createBridgeClient({ port: 8789, codeKey: "pr-bridge-code", app: "partner-radar" });
|
|
556
568
|
|
|
557
|
-
const picker = useEnginePicker();
|
|
569
|
+
const picker = useEnginePicker({ onOpenSettings: () => openSettings("ai") });
|
|
558
570
|
const b = useBridge(bridgeClient, { open, wantsLocal: engine !== "api", pickerOpen: picker.open,
|
|
559
571
|
// An engine that cannot run here (not on the server, and not "your machine only": the bridge may come) → the API one.
|
|
560
572
|
onDetected: (eng) => setEngine((cur) => (eng[cur] && !eng[cur].installed && !eng[cur].localOnly && eng.api?.installed ? "api" : cur)) });
|
|
@@ -574,8 +586,7 @@ async function send(text) {
|
|
|
574
586
|
}
|
|
575
587
|
}
|
|
576
588
|
|
|
577
|
-
async function onControl(kind) { // Stop / Remove on
|
|
578
|
-
picker.close(); // closes, focus on the chip (the confirm returns there)
|
|
589
|
+
async function onControl(kind) { // Stop / Remove on the bridge card in Settings
|
|
579
590
|
if (kind === "remove" && !(await confirm(…))) return;
|
|
580
591
|
try { turns.note(bridgeControlNote(kind, await b.control(kind)), { bridge: true }); }
|
|
581
592
|
catch (e) { turns.note(`Couldn't ${kind} the bridge: ${e.message}`); }
|
|
@@ -607,8 +618,8 @@ async function onControl(kind) { // Stop / Remove on Status
|
|
|
607
618
|
with the Pair form; another HTTP error leaves the state), `recheck()`. On the dev machine (`local`, default: the page is
|
|
608
619
|
on localhost) it probes nothing; `b.local` switches after mount, so the server's markup and the first render agree. The
|
|
609
620
|
client is the first render's for the hook's life (make it at module level: its data token is cached on it).
|
|
610
|
-
- **`bridgePickerProps(b, { latest, … })`** → `bridge`, `setup`, `statusActions` for `EnginePicker`: the dot and
|
|
611
|
-
rows,
|
|
621
|
+
- **`bridgePickerProps(b, { latest, … })`** → `bridge`, `setup`, `statusActions` for `EnginePicker`: the dot and the state
|
|
622
|
+
rows, Install or update per case (Allow / unblock / the Pair form + command / install / update), Check again, Stop and Remove
|
|
612
623
|
(`controls`). The words are `BRIDGE_SETUP_EN` (`labels` overrides); `outdatedDetail` and `installNote` are the surface's.
|
|
613
624
|
- What stays the surface's: which engines exist and what they cost, the request body, what each event does to its
|
|
614
625
|
messages, its confirm dialog.
|
|
@@ -633,14 +644,14 @@ streaming, bridge and sessions. Each piece is the better of the two surfaces tha
|
|
|
633
644
|
| Starters | `ChatStarters` | partner-radar | they wrap (radius 12): a long question as a nowrap pill is cut in a 400px panel; a fill-in example |
|
|
634
645
|
| Under an answer | `ChatMeta` | partner-radar | Copy · engine · seconds · cost |
|
|
635
646
|
| Errors | `ChatError`, `BridgeNotice` | partner-radar | a fix the user can take (sentence, command, Copy, the original folded); a bridge failure is one line |
|
|
636
|
-
| Engine | `EnginePicker` | partner-radar (
|
|
647
|
+
| Engine | `EnginePicker` + `EngineSettingsSection` | partner-radar (bridge setup and status) + admin (mark, models per engine) | see "The engine picker" |
|
|
637
648
|
| Frame, sessions | `AssistantHost`, `SessionRail` | (already the package's) | |
|
|
638
649
|
|
|
639
650
|
```tsx
|
|
640
651
|
import { AssistantChat, ChatAttach, EnginePicker, useChatTurns, useEnginePicker } from "@gemboss/ui/assistant"; // brings its CSS
|
|
641
652
|
|
|
642
653
|
const turns = useChatTurns(); // messages with ids; a turn is written BY ID
|
|
643
|
-
const picker = useEnginePicker();
|
|
654
|
+
const picker = useEnginePicker({ onOpenSettings: () => openSettings("ai") });
|
|
644
655
|
async function send(text: string) {
|
|
645
656
|
turns.say(text);
|
|
646
657
|
const id = turns.start();
|
|
@@ -1725,7 +1736,8 @@ an icon) · `.gemboss-ei-pick-text` › `.gemboss-ei-pick-head` (`.gemboss-ei-pi
|
|
|
1725
1736
|
`[data-autofocus]`, which both containers focus as they open (a `Dialog` without one gives the focus to its ✕). Under a finger
|
|
1726
1737
|
(`(pointer: coarse)`) the box does not take the focus by itself: the on-screen keyboard would cover the list. Escape in a box
|
|
1727
1738
|
with words clears them; in a list inside a list (the Popover's `onBack`) it steps back, as ← Back; otherwise the container
|
|
1728
|
-
closes and the focus goes back to what opened it
|
|
1739
|
+
closes and the focus goes back to what opened it (a `Dialog` opened by a click on a button that blurred itself, as Polaris'
|
|
1740
|
+
do, still finds it: the control the press landed on).
|
|
1729
1741
|
- Keys: ↑ ↓ move the highlight past locked rows, Enter picks; in the box Escape clears the words before the popup closes;
|
|
1730
1742
|
with no box the list is one tab stop and Home / End work too. One click picks.
|
|
1731
1743
|
- States: `loading` (skeleton rows, a first read), `reloading` (the last answer's rows kept, dimmed and `aria-busy`, nothing
|
package/catalog/editor.html
CHANGED
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
.cat-code summary{padding:10px 16px;font-size:13px;cursor:pointer;color:var(--gemboss-text-muted);border-top:1px solid var(--gemboss-divider);min-height:24px}
|
|
9
9
|
.cat-code pre,.cat-api{margin:0;padding:12px 16px;overflow:auto;background:#0f1012;color:#e8e8e6;font-size:12px;line-height:1.5;border-radius:0}
|
|
10
10
|
.cat-api{border-radius:12px;margin:0 0 16px}</style></head><body><div class="cat">
|
|
11
|
-
<h1>@gemboss/ui 0.
|
|
11
|
+
<h1>@gemboss/ui 0.53.0 · Editor</h1>
|
|
12
12
|
<p>Khung của mọi editor: <code>EditorFrame</code> (cột trái · khe kéo · preview · cột phải dock trên mép phải preview) và <code>EditorTopbar</code> (← · tiêu đề · cụm giữa · cụm phải · dòng trạng thái). Là đúng khung của theme / page / section editor trong admin. Gói chỉ vẽ KHUNG; chat, Configure, canvas, page picker, menu, Publish là của editor, đi vào bằng slot. Trang HTML thuần nạp <code>editor.css</code> + <code>editor-plain.js</code> rồi gọi <code>gembossUI.initEditorFrame()</code>: kéo khe (chuột, chạm, phím mũi tên / Home / End), đổi thiết bị, mở ⋯ và Publish ▾, ẩn cột trái, Chat | Preview trên điện thoại. <a href="index.html">← Catalog</a></p>
|
|
13
13
|
<h2>React</h2><pre class="cat-api"><code>import "@gemboss/ui/editor.css";
|
|
14
14
|
import { EditorFrame, EditorTopbar, EditorBack, EditorChatToggle, EditorPaneTabs, EditorSaveState, DeviceToggle } from "@gemboss/ui/editor";
|