nextpytk 0.4.7__tar.gz → 0.4.9__tar.gz

{nextpytk-0.4.7 → nextpytk-0.4.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nextpytk
-Version: 0.4.7
+Version: 0.4.9
 Summary: Accessible, declarative Tkinter applications from ordinary Python functions.
 Project-URL: Homepage, https://github.com/nishimotz/nextpytk
 Project-URL: Repository, https://github.com/nishimotz/nextpytk
@@ -35,7 +35,7 @@ Uses ttk widgets where available.
 
 ## Quick Start
 
-Start with an app where a button updates a message.
+Start with an app where a button updates its own label.
 
 ```bash
 pip install nextpytk
@@ -46,59 +46,48 @@ from nextpytk import TkApp
 
 app = TkApp(title="Hello")
 
-@app.status("msg")
-def msg():
-    return "Hello, world!"
+@app.button("hello")
+def on_hello():
+    return "world"
 
-@app.button("greet", label="Greet")
-def on_greet():
-    return {"msg": "Button clicked!"}
-
-app.run(layout=["msg", "greet"])
+app.run()
 ```
 
+That's it: a window appears with a button labeled `hello`. Press it and the
+label becomes `world`.
+
 ---
 
 ## How it works
 
-In nextpytk you register widgets by name and declare layout separately.
-
-This example registers two widgets: `msg` and `greet`.
-
-```python
-@app.status("msg")
-```
-
-`msg` is a status area that shows a message.
+The minimal example packs a lot in. Let's unpack it.
 
 ```python
-@app.button("greet", label="Greet")
+@app.button("hello")
 ```
 
-`greet` is a button labeled "Greet".
-
-Finally, name the display order:
+Registers a button named `hello`. When `label=` is omitted, the widget name is
+used as the button text.
 
 ```python
-app.run(layout=["msg", "greet"])
+def on_hello():
+    return "world"
 ```
 
-When you press the button, the callback returns this `dict`:
+The callback runs when the button is pressed. Returning a plain string updates
+that button's own label — it's sugar for `{"hello": "world"}`.
 
 ```python
-{"msg": "Button clicked!"}
+app.run()
 ```
 
-nextpytk merges that into the app `state`.
-
-Because `msg` is the name of the registered status area, its text becomes
-"Button clicked!".
+With no `layout=`, registered widgets are arranged automatically into a single
+column, so you don't have to declare one for a simple app.
 
-So the basic flow is:
+The basic flow is:
 
 * Register widgets by name
-* List those names in the layout
-* Return a `dict` from a callback
+* Return a `dict` (or a plain string) from a callback
 * `state` updates and matching widgets refresh
 
 ---
@@ -858,6 +847,7 @@ uv run python examples/disk_usage_flat_async.py       # ncdu-style viewer (async
 uv run python examples/paired_demo.py           # side-by-side paired layout with y-scroll sync
 uv run python examples/swap_demo.py             # dynamic region switching (Layout.target + @app.swap)
 uv run python examples/bottom_bar_demo.py       # pinned bottom bar (section side="bottom")
+uv run python examples/live_validation.py       # live validation via Tcl-var trace ingest (ingest_trace=True)
 ```
 
 ---
@@ -880,6 +870,10 @@ uv run python examples/bottom_bar_demo.py       # pinned bottom bar (section sid
 - **`CustomTkinter`**: Modern look via Canvas rendering. nextpytk takes the opposite approach: use native widgets and embed A11y from the start.
 - **`TkRouter`** (israel-dryer, author of ttkbootstrap): Declarative view routing with URL-style paths, animated transitions, and history stack. Complements nextpytk's `multiview` — routing vs widget composition.
 
+## Changelog
+
+See [CHANGES.md](./CHANGES.md) for the full release history.
+
 ## License
 
 MIT

{nextpytk-0.4.7 → nextpytk-0.4.9}/README.md

@@ -11,7 +11,7 @@ Uses ttk widgets where available.
 
 ## Quick Start
 
-Start with an app where a button updates a message.
+Start with an app where a button updates its own label.
 
 ```bash
 pip install nextpytk
@@ -22,59 +22,48 @@ from nextpytk import TkApp
 
 app = TkApp(title="Hello")
 
-@app.status("msg")
-def msg():
-    return "Hello, world!"
+@app.button("hello")
+def on_hello():
+    return "world"
 
-@app.button("greet", label="Greet")
-def on_greet():
-    return {"msg": "Button clicked!"}
-
-app.run(layout=["msg", "greet"])
+app.run()
 ```
 
+That's it: a window appears with a button labeled `hello`. Press it and the
+label becomes `world`.
+
 ---
 
 ## How it works
 
-In nextpytk you register widgets by name and declare layout separately.
-
-This example registers two widgets: `msg` and `greet`.
-
-```python
-@app.status("msg")
-```
-
-`msg` is a status area that shows a message.
+The minimal example packs a lot in. Let's unpack it.
 
 ```python
-@app.button("greet", label="Greet")
+@app.button("hello")
 ```
 
-`greet` is a button labeled "Greet".
-
-Finally, name the display order:
+Registers a button named `hello`. When `label=` is omitted, the widget name is
+used as the button text.
 
 ```python
-app.run(layout=["msg", "greet"])
+def on_hello():
+    return "world"
 ```
 
-When you press the button, the callback returns this `dict`:
+The callback runs when the button is pressed. Returning a plain string updates
+that button's own label — it's sugar for `{"hello": "world"}`.
 
 ```python
-{"msg": "Button clicked!"}
+app.run()
 ```
 
-nextpytk merges that into the app `state`.
-
-Because `msg` is the name of the registered status area, its text becomes
-"Button clicked!".
+With no `layout=`, registered widgets are arranged automatically into a single
+column, so you don't have to declare one for a simple app.
 
-So the basic flow is:
+The basic flow is:
 
 * Register widgets by name
-* List those names in the layout
-* Return a `dict` from a callback
+* Return a `dict` (or a plain string) from a callback
 * `state` updates and matching widgets refresh
 
 ---
@@ -834,6 +823,7 @@ uv run python examples/disk_usage_flat_async.py       # ncdu-style viewer (async
 uv run python examples/paired_demo.py           # side-by-side paired layout with y-scroll sync
 uv run python examples/swap_demo.py             # dynamic region switching (Layout.target + @app.swap)
 uv run python examples/bottom_bar_demo.py       # pinned bottom bar (section side="bottom")
+uv run python examples/live_validation.py       # live validation via Tcl-var trace ingest (ingest_trace=True)
 ```
 
 ---
@@ -856,6 +846,10 @@ uv run python examples/bottom_bar_demo.py       # pinned bottom bar (section sid
 - **`CustomTkinter`**: Modern look via Canvas rendering. nextpytk takes the opposite approach: use native widgets and embed A11y from the start.
 - **`TkRouter`** (israel-dryer, author of ttkbootstrap): Declarative view routing with URL-style paths, animated transitions, and history stack. Complements nextpytk's `multiview` — routing vs widget composition.
 
+## Changelog
+
+See [CHANGES.md](./CHANGES.md) for the full release history.
+
 ## License
 
 MIT

nextpytk-0.4.9/ROADMAP.md

@@ -0,0 +1,61 @@
+# ROADMAP — nextpytk
+
+> **Note:** Past release history lives in [CHANGES.md](./CHANGES.md).
+> This file is the forward-looking plan (near-term, then v0.5.0, then longer term).
+
+## Near term (post-0.4.8)
+
+### A11y
+
+- [ ] `@app.status` live-region behavior (ARIA `aria-live` equivalent / WCAG 4.1.3)
+- [ ] Tk 9.1 `tk accessible set_acc_*` real-device verification (9.1b0 + NVDA)
+- [ ] Role vocabulary mapping to Tk side
+- [ ] Automatic `emit_selection_change` (leverage `apply_state` knowing which widgets changed)
+
+### Type hints
+
+- [ ] Further TypedDict / Protocol coverage for decorator arguments
+- [ ] Fluent API equivalent to `_GridBuilder.columnconfigure`
+
+### Widget expansion
+
+- [ ] Per-widget `bind` for other widgets (`text`, `combobox`, `treeview`, `button`, etc.)
+- [ ] `@app.filepicker` — `filedialog` wrapper (schema/tool naming still open)
+
+### Layout DSL
+
+- [ ] CSS-grid-inspired layout API for 0.5.0: explicit `grid-template-columns` / `grid-template-rows` strings (e.g. `"1fr 2fr"`, `"auto 1fr"`), area-based placement, and gap tokens. Reduce misuse by making rows/columns and widget placement visually aligned in one declaration.
+- [ ] Wire visual Tab order for `side="bottom"` sections via `_wire_tab_order` (see v0.4.6 note in CHANGES.md).
+
+### Agent / LLM integration
+
+- [ ] Expose `schema()` as Function Calling definition (bind `sequence`, treeview column defs, etc.)
+- [ ] `@agent_tool` integration (GUI operations as agent vocabulary)
+- [ ] Surface `@app.filepicker` in `schema()` / tool vocabulary
+
+---
+
+## v0.5.0 — themes / chrome decoupling
+
+- Remove deprecated `theme=True/False` support; `theme` becomes `str` only.
+- Remove deprecated `EventSeq.DOUBLE_CLICK`; use `EventSeq.PRIMARY_DOUBLE_CLICK` or `DOUBLE_BUTTON_1`.
+- Remove deprecated index-order plural methods `col_weights`/`row_weights`/`col_minsizes`/`row_minsizes` and `Layout.cluster()` alias.
+- Decouple `Layout().header()` / `.status()` chrome from Kizashi-specific tokens so they render safely with any ttk theme (`"none"`, `"clam"`, etc.).
+- Extract Kizashi as a standalone ttk theme package so it can be proposed upstream or reused independently of nextpytk.
+
+---
+
+## Longer term
+
+### ttk Style layer
+
+- [ ] `Layout.style("my_button", background=..., font=...)` style definitions
+
+### Declarative components
+
+- [ ] `@app.component` decorator (React-like reuse, replacing `Layout`)
+- [ ] State type definitions and validation (no Pydantic)
+
+### Testing
+
+- [ ] WidgetSpec unit tests

{nextpytk-0.4.7 → nextpytk-0.4.9}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "nextpytk"
-version = "0.4.7"
+version = "0.4.9"
 description = "Accessible, declarative Tkinter applications from ordinary Python functions."
 readme = "README.md"
 requires-python = ">=3.13"