reflex-silverpoint-react 0.7.0__tar.gz → 0.8.0__tar.gz

{reflex_silverpoint_react-0.7.0 → reflex_silverpoint_react-0.8.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: reflex-silverpoint-react
-Version: 0.7.0
-Summary: The 60 silverpoint charts, the Dashboard, 17 UI components, palettes, 20 composed components and a Knight Lab timeline (Renaissance silverpoint drawing style) for Reflex, wrapping @silverpoint/react
+Version: 0.8.0
+Summary: The 60 silverpoint charts, the Dashboard, 38 UI, composed and overlay components, palettes and a Knight Lab timeline (Renaissance silverpoint drawing style) for Reflex, wrapping @silverpoint/react 0.8
 Author-email: Ernesto Crespo <ecrespo@gmail.com>
 License: MIT
 Project-URL: Homepage, https://github.com/ecrespo/reflex-silverpoint-react
@@ -18,13 +18,11 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: reflex>=0.10.0
 Provides-Extra: timeline
-Requires-Dist: reflex-knightlab-timeline>=0.1.2; extra == "timeline"
 Provides-Extra: dev
 Requires-Dist: build; extra == "dev"
 Requires-Dist: twine; extra == "dev"
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: ruff; extra == "dev"
-Requires-Dist: reflex-knightlab-timeline>=0.1.2; extra == "dev"
 Dynamic: license-file
 
 # reflex-silverpoint-react
@@ -36,17 +34,48 @@ prepared ground, tone built from hatching, and white heightening on the live val
 The hand-drawn irregularity lives only in the ornament. The data geometry is exact, and every chart
 has a `precision` mode that turns the inking off.
 
-It wraps [`@silverpoint/react`](https://www.npmjs.com/package/@silverpoint/react) 0.6.0 and exposes
+It wraps [`@silverpoint/react`](https://www.npmjs.com/package/@silverpoint/react) **0.8.0** and exposes
 **all 60 charts**, the **`Dashboard`** (a laid-out, linkable grid of charts), the **17 UI
-components** (buttons, inputs, tabs, cards, alerts…), the `SilverpointProvider`, both grounds
-(`silverpoint` and `cyanotype`), the interaction events, custom readouts and the imperative handle
-(SVG export and geometry) as Python.
-
-On top of that it adds, in Reflex: **palettes** for every chart and component, **20 composed
-components** built on silverpoint's own frames and tones (tables, overlays, toasts…), and the
-**Knight Lab timeline** drawn in silverpoint.
-
-### New in 0.7
+components** (buttons, inputs, tabs, cards, alerts…), the **12 composed components** (table,
+pagination, breadcrumb, avatar…), the **7 overlays** and the toaster (modal, drawer, popover,
+tooltip, select, dropdown menu, toast), the **palettes**, the **Knight Lab timeline**, the
+`SilverpointProvider`, both grounds (`silverpoint` and `cyanotype`), the interaction events, custom
+readouts and the imperative handle (SVG export and geometry) as Python.
+
+Everything it renders is an npm component of silverpoint, under its parity contract: the same
+markup React, Vue and Angular render.
+
+### New in 0.8.0
+
+- Wraps **`@silverpoint/react` 0.8.0**. silverpoint 0.8 adds agent access and changes no API this
+  package wraps, so the Python builders are unchanged.
+- **Agent access:** the `reflex-silverpoint` skill, a Claude plugin with the hosted silverpoint MCP
+  server, and `reflex-catalog.json`, the Reflex catalog silverpoint's agent catalog joins. See
+  [Use with AI](#use-with-ai).
+
+### New in 0.7.1
+
+- Wraps **`@silverpoint/react` 0.7.0** (0.7.0 wrapped 0.6.0). silverpoint 0.7 took this package's
+  palettes, composed components, overlays and timeline into the library itself, so they are now the
+  npm components, not Reflex-composed copies: same Python builders, the library's markup.
+- **Palettes** are the npm `palette` prop: they merge element → dashboard → provider field by field,
+  `silverpoint_provider(palette=...)` works, and `silverpoint_palette(...)` is a provider with a
+  palette. `check_palette()` measures the core's nine contrast pairs (the focus ring and the white
+  heightening included); `"ironGall"` names the `iron_gall` preset too.
+- **Composed components and overlays read `silverpoint_provider`**, as the `Sp` components do.
+  Overlays are a native `<dialog>` and the Popover API (no Radix); they render in place, so a
+  section's palette reaches them.
+- **Logical sides**: `side="start"`/`"end"` and `position="bottom-end"`…; `left`/`right` still work
+  with a `DeprecationWarning`. `sp_drawer(size=)` is `extent=`, `sp_popover(side_offset=)` is
+  `offset=`; `sp_modal` gains `label` and `dismissible`, `sp_result`/`sp_descriptions`
+  `heading_level`.
+- `sp_textarea(textarea_id=)` and `sp_input_number(input_id=)` are `id=` (deprecated aliases kept);
+  `sp_textarea` has no `on_blur`. `sp_collapse_item(on_toggle=)` receives the new open state (a bool).
+- **`sp_timeline`** is the npm `SpTimeline`: TimelineJS is an npm dependency of that component, so the
+  `[timeline]` extra pulls in nothing any more (it is kept so existing installs keep working).
+- `sort_rows()` follows the core's `uiSortRows` order (numbers first, then text by code point).
+
+### New in 0.7.0
 
 - **Reflex 0.10.0**, and therefore **Python 3.11 or later** (Python 3.10 is no longer supported).
   Reflex 0.10 removed `reflex component build`: stubs are regenerated with `scripts/make_stubs.py`.
@@ -63,7 +92,7 @@ components** built on silverpoint's own frames and tones (tables, overlays, toas
   `sp_trigger` as their drawn button. See [Composed components](#composed-components).
 - **`sp_timeline`** — Knight Lab TimelineJS drawn in silverpoint: a skin on the ground's colours and
   type, plus the ground's own hand-inked frames and tone tiles on its markers, eras and buttons.
-  Optional extra: `pip install "reflex-silverpoint-react[timeline]"`. See [Timeline](#timeline).
+  Optional extra (until 0.7.1): `pip install "reflex-silverpoint-react[timeline]"`. See [Timeline](#timeline).
 - `sp_surface`, `sp_glyph`: the building blocks, for components of your own.
 
 ### New in 0.6
@@ -396,19 +425,19 @@ silverpoint_palette(dashboard(...), sp_card(...), palette="indigo")  # a whole s
 ```
 
 Fields: `substrate`, `ink`, `ink_secondary`, `heighten`, `rule`, `grid`, `text`, `text_muted` and
-`focus` (the UI focus ring). Unset fields keep the ground's own. An element's own `palette` always
-wins over its section's. A palette is **monochrome by design**: tone is built from hatch density
-(Art. 6), so a chart has two inks (`ink` for the main series, `ink_secondary` for the second), never
-a colour per series. `precision` mode and the system's high-contrast modes still apply on top.
-`silverpoint_provider` takes no palette (it renders no element): use `silverpoint_palette`.
+`focus` (the UI focus ring). Unset fields keep the ground's own. Palettes merge field by field,
+element → dashboard → provider, so an element's own `palette` wins over its section's. A palette is
+**monochrome by design**: tone is built from hatch density (Art. 6), so a chart has two inks (`ink`
+for the main series, `ink_secondary` for the second), never a colour per series. `precision` mode and
+the system's high-contrast modes still apply on top. `silverpoint_palette(...)` is
+`silverpoint_provider(palette=...)` around the section.
 
 ## Composed components
 
-Components built in Reflex on silverpoint's markup contract: `@silverpoint/grounds/ui.css` draws its
-hand-inked frames, hatched tones and heightening on any element that follows it, so these are drawn
-with exactly the same pieces as the `Sp` components. They are **Reflex-only** (silverpoint's React,
-Vue and Angular adapters do not have them) and, unlike the `Sp` components, they do not read
-`silverpoint_provider`: pass `ground`, `substrate`, `mode` and `palette` explicitly.
+silverpoint 0.7's composed components and overlays, the npm components of `@silverpoint/react/ui`:
+native markup drawn by the core with the ground's hand-inked frames, hatched tones and
+heightening, exactly as the `Sp` components are. Like them they read `silverpoint_provider` (and
+the dashboard they sit in); a prop on the component always wins.
 
 ```python
 from reflex_silverpoint_react import sort_rows, sp_pagination, sp_table
@@ -428,7 +457,7 @@ sp_table(
 sp_pagination(total=240, current=State.page, on_change=State.set_page, show_total=True)
 ```
 
-| Level A (native) | |
+| Composed (native markup) | |
 |---|---|
 | `sp_table` | Card-framed table: small-caps header, tabular figures, hatched striping, sortable headers with `aria-sort` |
 | `sp_pagination` | Previous/next, first/last, a window around the current page (heightened); `on_change(page)` |
@@ -441,7 +470,7 @@ sp_pagination(total=240, current=State.page, on_change=State.set_page, show_tota
 | `sp_empty`, `sp_result` | Empty state; outcome with a drawn round mark |
 | `sp_textarea`, `sp_input_number` | On the `SpInput` contract; `on_change` receives the value (text or number) |
 
-| Level B (Radix primitives) | |
+| Overlays (`<dialog>`, Popover API) | |
 |---|---|
 | `sp_modal`, `sp_drawer` | Dialog on a card frame over a hatched backdrop; drawer from any edge |
 | `sp_popover`, `sp_tooltip` | Anchored content; tooltip on hover or keyboard focus |
@@ -449,10 +478,15 @@ sp_pagination(total=240, current=State.page, on_change=State.set_page, show_tota
 | `sp_dropdown_menu` | Commands with shortcuts, separators and labels; `on_select(key)` |
 | `sp_toast`, `sp_toaster` | Notices that stack in a corner; `error`/`warning` are announced assertively |
 
-Behaviour (focus trapping, keyboard, dismissal, positioning, ARIA) is Radix's, at the versions
-Reflex already installs. Overlays render in a portal at the end of `<body>`, outside any
-`silverpoint_palette` section, so give them `palette` directly. A string `trigger` becomes
-`sp_trigger(...)`, the drawn button that can forward Radix's props (`sp_button` cannot).
+Behaviour is the platform's: `showModal()` for the modal and the drawer (focus stays inside, Escape
+and the backdrop close it unless `dismissible=False`), the Popover API for the rest (light
+dismiss), keyboard and placement from `@silverpoint/core` (APG listbox and menu, typeahead, flip and
+shift). Overlays render in place (the top layer, no portal), so a section's palette reaches them.
+Sides are logical (`start`/`end`) and mirror in right-to-left text. An overlay clones its `trigger`
+with its ARIA and a toggling click, so the trigger must keep the props it is given: a native
+`rx.el.button`, or `sp_trigger(...)`, the drawn button strings become (`sp_button` drops them in
+silverpoint 0.7.0). `sp_trigger` does not read the provider: give it `ground`, `substrate`, `mode`
+and `palette`.
 
 ```python
 sp_modal(
@@ -471,15 +505,15 @@ sp_toaster(sp_toast("Saved", State.text, kind="success", open=State.toast_open,
 
 ## Timeline
 
-```bash
-pip install "reflex-silverpoint-react[timeline]"   # adds reflex-knightlab-timeline
-```
+The npm `SpTimeline` of `@silverpoint/react/timeline`. TimelineJS (`@knight-lab/timelinejs` 3.9.13)
+is an npm dependency of this component: Reflex installs it when a page uses `sp_timeline`, and no
+Python extra is needed. If it cannot be loaded, the component warns `SP025` and renders `fallback`.
 
 ```python
 from reflex_silverpoint_react import sp_timeline
 
 sp_timeline(
-    DATA,  # TimelineJS data: title, events, eras (or a TimelineData)
+    DATA,  # TimelineJS data: title, events, eras (or any object with to_dict())
     height=560,
     ground="silverpoint",
     substrate="cream",
@@ -561,10 +595,35 @@ The exported SVG carries its own ground colours, so it renders the same outside
 - Accessors are field names (strings). The JavaScript API also accepts functions; from Python, shape
   your rows instead.
 
+## Use with AI
+
+An assistant writes better `reflex-silverpoint-react` code with the **`reflex-silverpoint` skill**
+([`skills/reflex-silverpoint/`](skills/reflex-silverpoint/SKILL.md)): the builders and their
+snake_case props, State patterns, event payloads, the provider and palettes, composed components and
+overlays, the dashboard and the timeline. Its tables are generated from the package, and every Python
+example in it is imported and rendered by the tests.
+
+In Claude Code, the plugin installs the skill together with the hosted silverpoint MCP server
+(`https://silverpointweb.vercel.app/mcp`), which recommends charts, checks props and draws a chart
+as SVG before you write the code:
+
+```text
+/plugin marketplace add ecrespo/reflex-silverpoint-react
+/plugin install reflex-silverpoint@reflex-silverpoint
+```
+
+The MCP server alone: `claude mcp add --transport http silverpoint https://silverpointweb.vercel.app/mcp`.
+
+[`reflex-catalog.json`](reflex-catalog.json) is this package's catalog for agents: every chart and
+component builder with its props (Python name, JS name and type), the deprecated arguments it still
+accepts, the helpers, the package version and the silverpoint version it wraps. silverpoint's agent
+catalog joins it, so its MCP tools answer with the Reflex names too. `scripts/export_catalog.py`
+writes it, CI fails when it is stale, and each GitHub release carries it.
+
 ## Demo app
 
 ```bash
-uv venv && uv pip install -e ".[timeline]"
+uv venv && uv pip install -e .
 cd silverpoint_react_demo
 uv run reflex run
 ```

{reflex_silverpoint_react-0.7.0 → reflex_silverpoint_react-0.8.0}/README.md

@@ -7,17 +7,48 @@ prepared ground, tone built from hatching, and white heightening on the live val
 The hand-drawn irregularity lives only in the ornament. The data geometry is exact, and every chart
 has a `precision` mode that turns the inking off.
 
-It wraps [`@silverpoint/react`](https://www.npmjs.com/package/@silverpoint/react) 0.6.0 and exposes
+It wraps [`@silverpoint/react`](https://www.npmjs.com/package/@silverpoint/react) **0.8.0** and exposes
 **all 60 charts**, the **`Dashboard`** (a laid-out, linkable grid of charts), the **17 UI
-components** (buttons, inputs, tabs, cards, alerts…), the `SilverpointProvider`, both grounds
-(`silverpoint` and `cyanotype`), the interaction events, custom readouts and the imperative handle
-(SVG export and geometry) as Python.
-
-On top of that it adds, in Reflex: **palettes** for every chart and component, **20 composed
-components** built on silverpoint's own frames and tones (tables, overlays, toasts…), and the
-**Knight Lab timeline** drawn in silverpoint.
-
-### New in 0.7
+components** (buttons, inputs, tabs, cards, alerts…), the **12 composed components** (table,
+pagination, breadcrumb, avatar…), the **7 overlays** and the toaster (modal, drawer, popover,
+tooltip, select, dropdown menu, toast), the **palettes**, the **Knight Lab timeline**, the
+`SilverpointProvider`, both grounds (`silverpoint` and `cyanotype`), the interaction events, custom
+readouts and the imperative handle (SVG export and geometry) as Python.
+
+Everything it renders is an npm component of silverpoint, under its parity contract: the same
+markup React, Vue and Angular render.
+
+### New in 0.8.0
+
+- Wraps **`@silverpoint/react` 0.8.0**. silverpoint 0.8 adds agent access and changes no API this
+  package wraps, so the Python builders are unchanged.
+- **Agent access:** the `reflex-silverpoint` skill, a Claude plugin with the hosted silverpoint MCP
+  server, and `reflex-catalog.json`, the Reflex catalog silverpoint's agent catalog joins. See
+  [Use with AI](#use-with-ai).
+
+### New in 0.7.1
+
+- Wraps **`@silverpoint/react` 0.7.0** (0.7.0 wrapped 0.6.0). silverpoint 0.7 took this package's
+  palettes, composed components, overlays and timeline into the library itself, so they are now the
+  npm components, not Reflex-composed copies: same Python builders, the library's markup.
+- **Palettes** are the npm `palette` prop: they merge element → dashboard → provider field by field,
+  `silverpoint_provider(palette=...)` works, and `silverpoint_palette(...)` is a provider with a
+  palette. `check_palette()` measures the core's nine contrast pairs (the focus ring and the white
+  heightening included); `"ironGall"` names the `iron_gall` preset too.
+- **Composed components and overlays read `silverpoint_provider`**, as the `Sp` components do.
+  Overlays are a native `<dialog>` and the Popover API (no Radix); they render in place, so a
+  section's palette reaches them.
+- **Logical sides**: `side="start"`/`"end"` and `position="bottom-end"`…; `left`/`right` still work
+  with a `DeprecationWarning`. `sp_drawer(size=)` is `extent=`, `sp_popover(side_offset=)` is
+  `offset=`; `sp_modal` gains `label` and `dismissible`, `sp_result`/`sp_descriptions`
+  `heading_level`.
+- `sp_textarea(textarea_id=)` and `sp_input_number(input_id=)` are `id=` (deprecated aliases kept);
+  `sp_textarea` has no `on_blur`. `sp_collapse_item(on_toggle=)` receives the new open state (a bool).
+- **`sp_timeline`** is the npm `SpTimeline`: TimelineJS is an npm dependency of that component, so the
+  `[timeline]` extra pulls in nothing any more (it is kept so existing installs keep working).
+- `sort_rows()` follows the core's `uiSortRows` order (numbers first, then text by code point).
+
+### New in 0.7.0
 
 - **Reflex 0.10.0**, and therefore **Python 3.11 or later** (Python 3.10 is no longer supported).
   Reflex 0.10 removed `reflex component build`: stubs are regenerated with `scripts/make_stubs.py`.
@@ -34,7 +65,7 @@ components** built on silverpoint's own frames and tones (tables, overlays, toas
   `sp_trigger` as their drawn button. See [Composed components](#composed-components).
 - **`sp_timeline`** — Knight Lab TimelineJS drawn in silverpoint: a skin on the ground's colours and
   type, plus the ground's own hand-inked frames and tone tiles on its markers, eras and buttons.
-  Optional extra: `pip install "reflex-silverpoint-react[timeline]"`. See [Timeline](#timeline).
+  Optional extra (until 0.7.1): `pip install "reflex-silverpoint-react[timeline]"`. See [Timeline](#timeline).
 - `sp_surface`, `sp_glyph`: the building blocks, for components of your own.
 
 ### New in 0.6
@@ -367,19 +398,19 @@ silverpoint_palette(dashboard(...), sp_card(...), palette="indigo")  # a whole s
 ```
 
 Fields: `substrate`, `ink`, `ink_secondary`, `heighten`, `rule`, `grid`, `text`, `text_muted` and
-`focus` (the UI focus ring). Unset fields keep the ground's own. An element's own `palette` always
-wins over its section's. A palette is **monochrome by design**: tone is built from hatch density
-(Art. 6), so a chart has two inks (`ink` for the main series, `ink_secondary` for the second), never
-a colour per series. `precision` mode and the system's high-contrast modes still apply on top.
-`silverpoint_provider` takes no palette (it renders no element): use `silverpoint_palette`.
+`focus` (the UI focus ring). Unset fields keep the ground's own. Palettes merge field by field,
+element → dashboard → provider, so an element's own `palette` wins over its section's. A palette is
+**monochrome by design**: tone is built from hatch density (Art. 6), so a chart has two inks (`ink`
+for the main series, `ink_secondary` for the second), never a colour per series. `precision` mode and
+the system's high-contrast modes still apply on top. `silverpoint_palette(...)` is
+`silverpoint_provider(palette=...)` around the section.
 
 ## Composed components
 
-Components built in Reflex on silverpoint's markup contract: `@silverpoint/grounds/ui.css` draws its
-hand-inked frames, hatched tones and heightening on any element that follows it, so these are drawn
-with exactly the same pieces as the `Sp` components. They are **Reflex-only** (silverpoint's React,
-Vue and Angular adapters do not have them) and, unlike the `Sp` components, they do not read
-`silverpoint_provider`: pass `ground`, `substrate`, `mode` and `palette` explicitly.
+silverpoint 0.7's composed components and overlays, the npm components of `@silverpoint/react/ui`:
+native markup drawn by the core with the ground's hand-inked frames, hatched tones and
+heightening, exactly as the `Sp` components are. Like them they read `silverpoint_provider` (and
+the dashboard they sit in); a prop on the component always wins.
 
 ```python
 from reflex_silverpoint_react import sort_rows, sp_pagination, sp_table
@@ -399,7 +430,7 @@ sp_table(
 sp_pagination(total=240, current=State.page, on_change=State.set_page, show_total=True)
 ```
 
-| Level A (native) | |
+| Composed (native markup) | |
 |---|---|
 | `sp_table` | Card-framed table: small-caps header, tabular figures, hatched striping, sortable headers with `aria-sort` |
 | `sp_pagination` | Previous/next, first/last, a window around the current page (heightened); `on_change(page)` |
@@ -412,7 +443,7 @@ sp_pagination(total=240, current=State.page, on_change=State.set_page, show_tota
 | `sp_empty`, `sp_result` | Empty state; outcome with a drawn round mark |
 | `sp_textarea`, `sp_input_number` | On the `SpInput` contract; `on_change` receives the value (text or number) |
 
-| Level B (Radix primitives) | |
+| Overlays (`<dialog>`, Popover API) | |
 |---|---|
 | `sp_modal`, `sp_drawer` | Dialog on a card frame over a hatched backdrop; drawer from any edge |
 | `sp_popover`, `sp_tooltip` | Anchored content; tooltip on hover or keyboard focus |
@@ -420,10 +451,15 @@ sp_pagination(total=240, current=State.page, on_change=State.set_page, show_tota
 | `sp_dropdown_menu` | Commands with shortcuts, separators and labels; `on_select(key)` |
 | `sp_toast`, `sp_toaster` | Notices that stack in a corner; `error`/`warning` are announced assertively |
 
-Behaviour (focus trapping, keyboard, dismissal, positioning, ARIA) is Radix's, at the versions
-Reflex already installs. Overlays render in a portal at the end of `<body>`, outside any
-`silverpoint_palette` section, so give them `palette` directly. A string `trigger` becomes
-`sp_trigger(...)`, the drawn button that can forward Radix's props (`sp_button` cannot).
+Behaviour is the platform's: `showModal()` for the modal and the drawer (focus stays inside, Escape
+and the backdrop close it unless `dismissible=False`), the Popover API for the rest (light
+dismiss), keyboard and placement from `@silverpoint/core` (APG listbox and menu, typeahead, flip and
+shift). Overlays render in place (the top layer, no portal), so a section's palette reaches them.
+Sides are logical (`start`/`end`) and mirror in right-to-left text. An overlay clones its `trigger`
+with its ARIA and a toggling click, so the trigger must keep the props it is given: a native
+`rx.el.button`, or `sp_trigger(...)`, the drawn button strings become (`sp_button` drops them in
+silverpoint 0.7.0). `sp_trigger` does not read the provider: give it `ground`, `substrate`, `mode`
+and `palette`.
 
 ```python
 sp_modal(
@@ -442,15 +478,15 @@ sp_toaster(sp_toast("Saved", State.text, kind="success", open=State.toast_open,
 
 ## Timeline
 
-```bash
-pip install "reflex-silverpoint-react[timeline]"   # adds reflex-knightlab-timeline
-```
+The npm `SpTimeline` of `@silverpoint/react/timeline`. TimelineJS (`@knight-lab/timelinejs` 3.9.13)
+is an npm dependency of this component: Reflex installs it when a page uses `sp_timeline`, and no
+Python extra is needed. If it cannot be loaded, the component warns `SP025` and renders `fallback`.
 
 ```python
 from reflex_silverpoint_react import sp_timeline
 
 sp_timeline(
-    DATA,  # TimelineJS data: title, events, eras (or a TimelineData)
+    DATA,  # TimelineJS data: title, events, eras (or any object with to_dict())
     height=560,
     ground="silverpoint",
     substrate="cream",
@@ -532,10 +568,35 @@ The exported SVG carries its own ground colours, so it renders the same outside
 - Accessors are field names (strings). The JavaScript API also accepts functions; from Python, shape
   your rows instead.
 
+## Use with AI
+
+An assistant writes better `reflex-silverpoint-react` code with the **`reflex-silverpoint` skill**
+([`skills/reflex-silverpoint/`](skills/reflex-silverpoint/SKILL.md)): the builders and their
+snake_case props, State patterns, event payloads, the provider and palettes, composed components and
+overlays, the dashboard and the timeline. Its tables are generated from the package, and every Python
+example in it is imported and rendered by the tests.
+
+In Claude Code, the plugin installs the skill together with the hosted silverpoint MCP server
+(`https://silverpointweb.vercel.app/mcp`), which recommends charts, checks props and draws a chart
+as SVG before you write the code:
+
+```text
+/plugin marketplace add ecrespo/reflex-silverpoint-react
+/plugin install reflex-silverpoint@reflex-silverpoint
+```
+
+The MCP server alone: `claude mcp add --transport http silverpoint https://silverpointweb.vercel.app/mcp`.
+
+[`reflex-catalog.json`](reflex-catalog.json) is this package's catalog for agents: every chart and
+component builder with its props (Python name, JS name and type), the deprecated arguments it still
+accepts, the helpers, the package version and the silverpoint version it wraps. silverpoint's agent
+catalog joins it, so its MCP tools answer with the Reflex names too. `scripts/export_catalog.py`
+writes it, CI fails when it is stale, and each GitHub release carries it.
+
 ## Demo app
 
 ```bash
-uv venv && uv pip install -e ".[timeline]"
+uv venv && uv pip install -e .
 cd silverpoint_react_demo
 uv run reflex run
 ```

{reflex_silverpoint_react-0.7.0 → reflex_silverpoint_react-0.8.0}/custom_components/reflex_silverpoint_react/__init__.py

@@ -1,7 +1,8 @@
 """reflex-silverpoint-react: silverpoint charts and UI components for Reflex.
 
 Charts and interface components drawn in the manner of a Renaissance silverpoint drawing,
-wrapping ``@silverpoint/react``.
+wrapping ``@silverpoint/react`` 0.8.0: the 60 charts, the dashboard, the 38 UI, composed and overlay
+components, the palettes and the Knight Lab timeline.
 """
 
 from .base import (
@@ -11,6 +12,7 @@ from .base import (
     GroundName,
     SilverpointChart,
     SilverpointProvider,
+    silverpoint_palette,
     silverpoint_provider,
 )
 from .catalog import CHARTS, COMMON_PROPS, FAMILIES, ChartInfo, PropDoc, chart_by_name, chart_by_slug
@@ -138,6 +140,18 @@ from .charts import (
     wind_rose,
 )
 from .composed import (
+    SpAvatar,
+    SpAvatarGroup,
+    SpBreadcrumb,
+    SpCollapse,
+    SpCollapseItem,
+    SpDescriptions,
+    SpEmpty,
+    SpResult,
+    SpStatistic,
+    SpTable,
+    SpTextarea,
+    SpTimelineList,
     sort_rows,
     sp_avatar,
     sp_avatar_group,
@@ -165,6 +179,15 @@ from .dashboard import (
 )
 from .helpers import chart_ref, download_svg, get_geometry, get_svg, tooltip_template
 from .overlays import (
+    SpDrawer,
+    SpDropdownMenu,
+    SpModal,
+    SpPopover,
+    SpSelect,
+    SpToast,
+    SpToaster,
+    SpTooltip,
+    SpTrigger,
     sp_drawer,
     sp_dropdown_menu,
     sp_modal,
@@ -176,13 +199,15 @@ from .overlays import (
     sp_trigger,
 )
 from .palette import (
+    PALETTE_JS_FIELDS,
+    PALETTE_PAIRS,
     PALETTE_PROPERTIES,
     PALETTES,
     Palette,
     check_palette,
     contrast_ratio,
     palette_css,
-    silverpoint_palette,
+    palette_prop,
 )
 from .surfaces import (
     SpGlyph,
@@ -194,7 +219,7 @@ from .surfaces import (
     sp_pagination,
     sp_surface,
 )
-from .timeline import sp_timeline, timeline_available
+from .timeline import TIMELINEJS_VERSION, SpTimeline, sp_timeline, timeline_available
 from .ui import (
     SILVERPOINT_UI_STYLESHEET,
     SilverpointUi,
@@ -254,11 +279,14 @@ __all__ = [
     "DASHBOARD_DEFAULTS",
     "FAMILIES",
     "PALETTES",
+    "PALETTE_JS_FIELDS",
+    "PALETTE_PAIRS",
     "PALETTE_PROPERTIES",
     "SILVERPOINT_LIBRARY",
     "SILVERPOINT_STYLESHEETS",
     "SILVERPOINT_UI_STYLESHEET",
     "SILVERPOINT_VERSION",
+    "TIMELINEJS_VERSION",
     "UI_COMMON_PROPS",
     "UI_COMPONENTS",
     "UI_DEMOS",
@@ -321,27 +349,49 @@ __all__ = [
     "SilverpointUi",
     "SlopeChart",
     "SpAlert",
+    "SpAvatar",
+    "SpAvatarGroup",
     "SpBadge",
+    "SpBreadcrumb",
     "SpButton",
     "SpCard",
     "SpCheckbox",
+    "SpCollapse",
+    "SpCollapseItem",
+    "SpDescriptions",
     "SpDivider",
+    "SpDrawer",
+    "SpDropdownMenu",
+    "SpEmpty",
     "SpGlyph",
     "SpInput",
     "SpInputNumber",
+    "SpModal",
     "SpPagination",
+    "SpPopover",
     "SpProgress",
     "SpRadioGroup",
     "SpRate",
+    "SpResult",
     "SpSegmented",
+    "SpSelect",
     "SpSkeleton",
     "SpSlider",
+    "SpStatistic",
     "SpSteps",
     "SpSurface",
     "SpSwitch",
     "SpTabPanel",
+    "SpTable",
     "SpTabs",
     "SpTag",
+    "SpTextarea",
+    "SpTimeline",
+    "SpTimelineList",
+    "SpToast",
+    "SpToaster",
+    "SpTooltip",
+    "SpTrigger",
     "SparklineRows",
     "SquarifiedTreemap",
     "StackedBarChart",
@@ -405,6 +455,7 @@ __all__ = [
     "network_node",
     "orbit_chart",
     "palette_css",
+    "palette_prop",
     "parallel_coordinates_chart",
     "polar_bar_chart",
     "polar_line_chart",

reflex_silverpoint_react-0.8.0/custom_components/reflex_silverpoint_react/assets/trigger.jsx

@@ -0,0 +1,63 @@
+/* reflex-silverpoint-react — sp_trigger: a native <button> drawn as SpButton, that keeps every prop.
+ *
+ * An overlay of @silverpoint/react clones its trigger with aria-haspopup, aria-expanded,
+ * aria-controls, onPointerDown and onClick (useTrigger, REQ-500). SpButton 0.7.0 keeps only its own
+ * props, so those would be lost on it; this button renders the very tree @silverpoint/core's
+ * uiButtonView builds (resolveUi resolves ground, substrate, mode, size, frame variant and palette)
+ * and adds everything else it is given to the native element.
+ */
+const SP_TRIGGER_ATTRS = { class: "className", for: "htmlFor", readonly: "readOnly", tabindex: "tabIndex" };
+
+function spTriggerStyle(text) {
+  const out = {};
+  for (const declaration of (text || "").split(";")) {
+    const colon = declaration.indexOf(":");
+    if (colon > 0) out[declaration.slice(0, colon).trim()] = declaration.slice(colon + 1).trim();
+  }
+  return out;
+}
+
+function spTriggerNode(node, content, extra) {
+  if ("text" in node) return node.text;
+  if ("slot" in node) return node.slot === "content" ? content : null;
+  const props = {};
+  for (const [name, value] of Object.entries(node.attrs)) {
+    if (value === undefined) continue;
+    props[SP_TRIGGER_ATTRS[name] || name] = name === "style" ? spTriggerStyle(value) : value;
+  }
+  if (extra) {
+    const { style, ...rest } = extra;
+    Object.assign(props, rest);
+    if (style) props.style = { ...(props.style || {}), ...style };
+  }
+  return createElement(node.tag, props, ...node.children.map((child) => spTriggerNode(child, content)));
+}
+
+function useSpTriggerForced() {
+  const [forced, setForced] = useState(false);
+  useEffect(() => {
+    if (typeof matchMedia !== "function") return undefined;
+    const query = matchMedia(FORCED_PRECISION_QUERY);
+    const update = () => setForced(query.matches);
+    update();
+    query.addEventListener?.("change", update);
+    return () => query.removeEventListener?.("change", update);
+  }, []);
+  return forced;
+}
+
+const SilverpointTrigger = forwardRef(function SilverpointTrigger(
+  { ground, substrate, mode, size, seed, palette, variant, chevron, disabled, label, children, className, id, ...rest },
+  ref,
+) {
+  const forcedPrecision = useSpTriggerForced();
+  const props = { ground, substrate, mode, size, seed, palette, variant, disabled, label, className, id, type: "button" };
+  const resolved = resolveUi(props, { forcedPrecision });
+  const text = typeof children === "string" || typeof children === "number" ? String(children) : children == null ? undefined : "·";
+  const view = uiButtonView(props, resolved, { text });
+  // The chevron sits beside the label, as SpButton's own danger cross does.
+  const tree = chevron
+    ? { ...view, children: [...view.children, { tag: "svg", attrs: { part: "sp-mark", "data-glyph": "chevronDown", viewBox: "0 0 16 16", "aria-hidden": "true" }, children: [{ tag: "path", attrs: { d: UI_GLYPHS.chevronDown }, children: [] }] }] }
+    : view;
+  return spTriggerNode(tree, children, { ...rest, ref });
+});