pyweft 0.2.0__tar.gz → 0.3.0__tar.gz

{pyweft-0.2.0 → pyweft-0.3.0}/.gitignore

@@ -8,3 +8,4 @@ dist-desktop/
 .venv/
 CLAUDE.md
 PROMPTS.md
+website/_build/

{pyweft-0.2.0 → pyweft-0.3.0}/CHANGELOG.md

@@ -8,6 +8,27 @@ releasing moves them under the new version (see [RELEASING.md](RELEASING.md)).
 
 ## Unreleased
 
+## 0.3.0
+
+- **`pyweft.http`**: call web APIs and load the app's data files, with the
+  same code in the browser (the page's fetch) and on the desktop (the
+  standard library). `get_json`, `get`/`post`/`put`/`patch`/`delete`,
+  `request`; JSON, form and text bodies, query parameters, timeouts. A
+  relative URL is a file the app ships (`assets/prices.json`).
+- **`pyweft.storage`**: keep data between visits: `get`, `set`, `delete`,
+  `has`, `keys`, `clear`, for any JSON value. The browser's local storage,
+  kept apart per app; on the desktop, a JSON file in the user's data
+  folder; in tests, memory.
+- The todo example remembers its list, and the tutorial has a step for it.
+- The todo and shop examples are restyled with Tailwind CSS (built with
+  its CLI), in light and dark, and work at phone width. The shop has a
+  dashboard, an orders table and a reusable status badge.
+
+## 0.2.1
+
+- The PyPI page installs from PyPI, and its links to the guide and the
+  toolkit work there.
+
 ## 0.2.0
 
 The first release. (It starts at 0.2.0 because an earlier, unrelated

{pyweft-0.2.0 → pyweft-0.3.0}/PKG-INFO

@@ -1,9 +1,9 @@
 Metadata-Version: 2.5
 Name: pyweft
-Version: 0.2.0
+Version: 0.3.0
 Summary: A UI framework for Python: XML templates, Python code-behind, one render core for web, desktop and mobile.
 Project-URL: Homepage, https://github.com/prassanthn/PyWeft
-Project-URL: Documentation, https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md
+Project-URL: Documentation, https://prassanthn.github.io/PyWeft/
 Project-URL: Issues, https://github.com/prassanthn/PyWeft/issues
 Author: Prassanth Nicholas
 License-Expression: MIT
@@ -36,6 +36,12 @@ running on your machine. No JavaScript to write, no build step.
 
 *PyWeft: the weft is the thread woven through the warp to make fabric.*
 
+**[Website](https://prassanthn.github.io/PyWeft/)**: a step-by-step
+[tutorial](https://prassanthn.github.io/PyWeft/tutorial/), the
+[guide](https://prassanthn.github.io/PyWeft/guide/), and the
+[controls](https://prassanthn.github.io/PyWeft/live/gallery/) and
+[examples](https://prassanthn.github.io/PyWeft/examples/) running live.
+
 ```xml
 <template>
   <div>
@@ -56,7 +62,7 @@ is plain Python fields, and the page updates itself after every event.
 
 > **Status:** a working proof of concept. Web apps and desktop apps (run
 > locally or built into a program to hand out) work today. APIs may still
-> change. Not on PyPI yet, so you install from GitHub (below).
+> change.
 
 ## Quick start
 
@@ -64,7 +70,7 @@ You need Python 3.10 or newer. With [uv](https://docs.astral.sh/uv/):
 
 ```bash
 uv init myproject && cd myproject
-uv add git+https://github.com/prassanthn/PyWeft.git
+uv add pyweft
 uv run pyweft new myapp
 uv run pyweft run myapp
 ```
@@ -76,7 +82,7 @@ time, cached after that); then it comes alive.
 With pip instead:
 
 ```bash
-pip install git+https://github.com/prassanthn/PyWeft.git
+pip install pyweft
 pyweft new myapp
 pyweft run myapp
 ```
@@ -130,13 +136,13 @@ height = 800
 
 ## Ready-made controls (no HTML or CSS needed)
 
-[`pyweft-ui`](packages/pyweft-ui/README.md) gives you styled, accessible
+[`pyweft-ui`](https://github.com/prassanthn/PyWeft/blob/main/packages/pyweft-ui/README.md) gives you styled, accessible
 controls as components: buttons, text fields, selects, checkboxes, switches,
 cards, tabs, sortable tables, dialogs, alerts, toasts, layout and light/dark
 themes.
 
 ```bash
-uv add "pyweft-ui @ git+https://github.com/prassanthn/PyWeft.git#subdirectory=packages/pyweft-ui"
+uv add pyweft-ui
 ```
 
 Add `"pyweft-ui"` to the `dependencies` list in `myapp/pyproject.toml`, then
@@ -208,6 +214,9 @@ To see every control live, clone this repository and run
 - **Files and dialogs:** `pyweft.dialogs` opens and saves files and asks for
   confirmation with the same code on both targets: the browser's picker and
   downloads on the web, the system's own dialogs on the desktop.
+- **Data in and out:** `pyweft.http` calls web APIs and loads your app's
+  data files, and `pyweft.storage` keeps settings and lists between visits,
+  with the same code in the browser and on the desktop.
 - **A fast dev loop:** hot reload that keeps your app's state, and readable
   errors that point to your `.weft` file and line.
 - **Fast first load:** your app's first screen is rendered ahead of time and
@@ -217,20 +226,21 @@ To see every control live, clone this repository and run
 
 | You want to | Read |
 |---|---|
-| Learn the basics: state, templates, events | [Getting started](docs/getting-started.md), sections 1–3 |
-| Run code when a component appears, updates or goes away | [Lifecycle](docs/getting-started.md#lifecycle-when-your-code-runs) |
-| Split an app into components, use slots | [Composing components](docs/getting-started.md#4-composing-components) |
-| Build an app with several pages | [Pages and navigation](docs/getting-started.md#pages-and-navigation) |
-| Handle forms and keyboard input | [Binding form controls](docs/getting-started.md#binding-form-controls), [event modifiers](docs/getting-started.md#event-modifiers) |
-| Load data, run async code, do heavy work | [Async handlers](docs/getting-started.md#async-handlers-and-background-work), [`run_in_background`](docs/getting-started.md#heavy-work-run_in_background) |
-| Style with Tailwind or Bootstrap | [Using CSS frameworks](docs/getting-started.md#using-css-frameworks) |
-| Build screens with the ready-made controls | [pyweft-ui guide](packages/pyweft-ui/docs/guide.md), then the [reference](packages/pyweft-ui/README.md) |
-| Deploy your app | [Building for deployment](docs/getting-started.md#building-for-deployment) |
-| Run it as a desktop app | [A desktop app](docs/getting-started.md#a-desktop-app-pyweft-run---desktop) |
-| Hand out a desktop app (`.exe`, `.app`) | [Handing out a desktop app](docs/getting-started.md#handing-out-a-desktop-app-pyweft-build---desktop) |
-| Open and save files, ask for confirmation | [Files and dialogs](docs/getting-started.md#files-and-dialogs) |
-| Name the app, give it an icon | [The app's title and icon](docs/getting-started.md#the-apps-title-and-icon) |
-| Test components without a browser | [Using the engine from plain Python](docs/getting-started.md#6-using-the-engine-from-plain-python) |
+| Learn the basics: state, templates, events | [Getting started](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md), sections 1–3 |
+| Run code when a component appears, updates or goes away | [Lifecycle](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#lifecycle-when-your-code-runs) |
+| Split an app into components, use slots | [Composing components](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#4-composing-components) |
+| Build an app with several pages | [Pages and navigation](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#pages-and-navigation) |
+| Handle forms and keyboard input | [Binding form controls](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#binding-form-controls), [event modifiers](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#event-modifiers) |
+| Load data, run async code, do heavy work | [Async handlers](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#async-handlers-and-background-work), [`run_in_background`](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#heavy-work-run_in_background) |
+| Style with Tailwind or Bootstrap | [Using CSS frameworks](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#using-css-frameworks) |
+| Build screens with the ready-made controls | [pyweft-ui guide](https://github.com/prassanthn/PyWeft/blob/main/packages/pyweft-ui/docs/guide.md), then the [reference](https://github.com/prassanthn/PyWeft/blob/main/packages/pyweft-ui/README.md) |
+| Deploy your app | [Building for deployment](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#building-for-deployment) |
+| Run it as a desktop app | [A desktop app](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#a-desktop-app-pyweft-run---desktop) |
+| Hand out a desktop app (`.exe`, `.app`) | [Handing out a desktop app](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#handing-out-a-desktop-app-pyweft-build---desktop) |
+| Open and save files, ask for confirmation | [Files and dialogs](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#files-and-dialogs) |
+| Call web APIs, save data between visits | [Loading data](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#loading-data-pywefthttp), [saving data](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#saving-data-between-visits-pyweftstorage) |
+| Name the app, give it an icon | [The app's title and icon](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#the-apps-title-and-icon) |
+| Test components without a browser | [Using the engine from plain Python](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#6-using-the-engine-from-plain-python) |
 
 `examples/todo/` is a small complete app, and `examples/shop/` one with
 pages; run them from a clone with `uv run pyweft run examples/todo`.
@@ -279,15 +289,25 @@ uv run pyweft run packages/pyweft-ui/gallery  # every control
 
 With pip: `pip install -e ".[dev]"` and `pip install -e packages/pyweft-ui`.
 
-Releases go to PyPI by pushing a version tag; [RELEASING.md](RELEASING.md)
-has the steps, and [CHANGELOG.md](CHANGELOG.md) what each release changed.
+Releases go to PyPI by pushing a version tag; [RELEASING.md](https://github.com/prassanthn/PyWeft/blob/main/RELEASING.md)
+has the steps, and [CHANGELOG.md](https://github.com/prassanthn/PyWeft/blob/main/CHANGELOG.md) what each release changed.
+
+The website is rebuilt and published on every push to `main`. To build it
+locally:
+
+```bash
+uv sync --group website
+uv run python website/build.py
+uv run python -m http.server -d website/_build/site    # http://127.0.0.1:8000/
+```
 
 ```
 src/pyweft/           the framework (zero runtime dependencies)
   static/             the browser side: runtime.js, the page shell, the worker
 packages/pyweft-ui/   the control toolkit, released as its own package
-docs/                 the guide
+docs/                 the guide (the website splits it into pages)
 examples/             a headless demo, the todo app and the shop (pages)
+website/              the website: home page, tutorial, build script
 tests/                the framework's tests
 ```
 
@@ -311,9 +331,9 @@ handlers and Web Worker background work; file and confirmation dialogs on
 both targets; the app's title and icon, and window settings; scoped styles
 and CSS framework support; the `pyweft` CLI with hot reload, static builds
 and pre-rendered first screens; `pyweft-ui` with 22 keyboard-accessible
-controls and a gallery.
+controls and a gallery; both released on PyPI.
 
-**Next:** publishing `pyweft` and `pyweft-ui` to PyPI; more controls (menus,
+**Next:** more controls (menus,
 a date picker, form validation); installers (`.msi`, `.dmg`) and code
 signing for desktop apps.
 
@@ -321,4 +341,4 @@ signing for desktop apps.
 
 ## License
 
-MIT. See [LICENSE](LICENSE).
+MIT. See [LICENSE](https://github.com/prassanthn/PyWeft/blob/main/LICENSE).

{pyweft-0.2.0 → pyweft-0.3.0}/README.md

@@ -7,6 +7,12 @@ running on your machine. No JavaScript to write, no build step.
 
 *PyWeft: the weft is the thread woven through the warp to make fabric.*
 
+**[Website](https://prassanthn.github.io/PyWeft/)**: a step-by-step
+[tutorial](https://prassanthn.github.io/PyWeft/tutorial/), the
+[guide](https://prassanthn.github.io/PyWeft/guide/), and the
+[controls](https://prassanthn.github.io/PyWeft/live/gallery/) and
+[examples](https://prassanthn.github.io/PyWeft/examples/) running live.
+
 ```xml
 <template>
   <div>
@@ -27,7 +33,7 @@ is plain Python fields, and the page updates itself after every event.
 
 > **Status:** a working proof of concept. Web apps and desktop apps (run
 > locally or built into a program to hand out) work today. APIs may still
-> change. Not on PyPI yet, so you install from GitHub (below).
+> change.
 
 ## Quick start
 
@@ -35,7 +41,7 @@ You need Python 3.10 or newer. With [uv](https://docs.astral.sh/uv/):
 
 ```bash
 uv init myproject && cd myproject
-uv add git+https://github.com/prassanthn/PyWeft.git
+uv add pyweft
 uv run pyweft new myapp
 uv run pyweft run myapp
 ```
@@ -47,7 +53,7 @@ time, cached after that); then it comes alive.
 With pip instead:
 
 ```bash
-pip install git+https://github.com/prassanthn/PyWeft.git
+pip install pyweft
 pyweft new myapp
 pyweft run myapp
 ```
@@ -101,13 +107,13 @@ height = 800
 
 ## Ready-made controls (no HTML or CSS needed)
 
-[`pyweft-ui`](packages/pyweft-ui/README.md) gives you styled, accessible
+[`pyweft-ui`](https://github.com/prassanthn/PyWeft/blob/main/packages/pyweft-ui/README.md) gives you styled, accessible
 controls as components: buttons, text fields, selects, checkboxes, switches,
 cards, tabs, sortable tables, dialogs, alerts, toasts, layout and light/dark
 themes.
 
 ```bash
-uv add "pyweft-ui @ git+https://github.com/prassanthn/PyWeft.git#subdirectory=packages/pyweft-ui"
+uv add pyweft-ui
 ```
 
 Add `"pyweft-ui"` to the `dependencies` list in `myapp/pyproject.toml`, then
@@ -179,6 +185,9 @@ To see every control live, clone this repository and run
 - **Files and dialogs:** `pyweft.dialogs` opens and saves files and asks for
   confirmation with the same code on both targets: the browser's picker and
   downloads on the web, the system's own dialogs on the desktop.
+- **Data in and out:** `pyweft.http` calls web APIs and loads your app's
+  data files, and `pyweft.storage` keeps settings and lists between visits,
+  with the same code in the browser and on the desktop.
 - **A fast dev loop:** hot reload that keeps your app's state, and readable
   errors that point to your `.weft` file and line.
 - **Fast first load:** your app's first screen is rendered ahead of time and
@@ -188,20 +197,21 @@ To see every control live, clone this repository and run
 
 | You want to | Read |
 |---|---|
-| Learn the basics: state, templates, events | [Getting started](docs/getting-started.md), sections 1–3 |
-| Run code when a component appears, updates or goes away | [Lifecycle](docs/getting-started.md#lifecycle-when-your-code-runs) |
-| Split an app into components, use slots | [Composing components](docs/getting-started.md#4-composing-components) |
-| Build an app with several pages | [Pages and navigation](docs/getting-started.md#pages-and-navigation) |
-| Handle forms and keyboard input | [Binding form controls](docs/getting-started.md#binding-form-controls), [event modifiers](docs/getting-started.md#event-modifiers) |
-| Load data, run async code, do heavy work | [Async handlers](docs/getting-started.md#async-handlers-and-background-work), [`run_in_background`](docs/getting-started.md#heavy-work-run_in_background) |
-| Style with Tailwind or Bootstrap | [Using CSS frameworks](docs/getting-started.md#using-css-frameworks) |
-| Build screens with the ready-made controls | [pyweft-ui guide](packages/pyweft-ui/docs/guide.md), then the [reference](packages/pyweft-ui/README.md) |
-| Deploy your app | [Building for deployment](docs/getting-started.md#building-for-deployment) |
-| Run it as a desktop app | [A desktop app](docs/getting-started.md#a-desktop-app-pyweft-run---desktop) |
-| Hand out a desktop app (`.exe`, `.app`) | [Handing out a desktop app](docs/getting-started.md#handing-out-a-desktop-app-pyweft-build---desktop) |
-| Open and save files, ask for confirmation | [Files and dialogs](docs/getting-started.md#files-and-dialogs) |
-| Name the app, give it an icon | [The app's title and icon](docs/getting-started.md#the-apps-title-and-icon) |
-| Test components without a browser | [Using the engine from plain Python](docs/getting-started.md#6-using-the-engine-from-plain-python) |
+| Learn the basics: state, templates, events | [Getting started](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md), sections 1–3 |
+| Run code when a component appears, updates or goes away | [Lifecycle](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#lifecycle-when-your-code-runs) |
+| Split an app into components, use slots | [Composing components](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#4-composing-components) |
+| Build an app with several pages | [Pages and navigation](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#pages-and-navigation) |
+| Handle forms and keyboard input | [Binding form controls](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#binding-form-controls), [event modifiers](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#event-modifiers) |
+| Load data, run async code, do heavy work | [Async handlers](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#async-handlers-and-background-work), [`run_in_background`](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#heavy-work-run_in_background) |
+| Style with Tailwind or Bootstrap | [Using CSS frameworks](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#using-css-frameworks) |
+| Build screens with the ready-made controls | [pyweft-ui guide](https://github.com/prassanthn/PyWeft/blob/main/packages/pyweft-ui/docs/guide.md), then the [reference](https://github.com/prassanthn/PyWeft/blob/main/packages/pyweft-ui/README.md) |
+| Deploy your app | [Building for deployment](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#building-for-deployment) |
+| Run it as a desktop app | [A desktop app](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#a-desktop-app-pyweft-run---desktop) |
+| Hand out a desktop app (`.exe`, `.app`) | [Handing out a desktop app](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#handing-out-a-desktop-app-pyweft-build---desktop) |
+| Open and save files, ask for confirmation | [Files and dialogs](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#files-and-dialogs) |
+| Call web APIs, save data between visits | [Loading data](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#loading-data-pywefthttp), [saving data](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#saving-data-between-visits-pyweftstorage) |
+| Name the app, give it an icon | [The app's title and icon](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#the-apps-title-and-icon) |
+| Test components without a browser | [Using the engine from plain Python](https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md#6-using-the-engine-from-plain-python) |
 
 `examples/todo/` is a small complete app, and `examples/shop/` one with
 pages; run them from a clone with `uv run pyweft run examples/todo`.
@@ -250,15 +260,25 @@ uv run pyweft run packages/pyweft-ui/gallery  # every control
 
 With pip: `pip install -e ".[dev]"` and `pip install -e packages/pyweft-ui`.
 
-Releases go to PyPI by pushing a version tag; [RELEASING.md](RELEASING.md)
-has the steps, and [CHANGELOG.md](CHANGELOG.md) what each release changed.
+Releases go to PyPI by pushing a version tag; [RELEASING.md](https://github.com/prassanthn/PyWeft/blob/main/RELEASING.md)
+has the steps, and [CHANGELOG.md](https://github.com/prassanthn/PyWeft/blob/main/CHANGELOG.md) what each release changed.
+
+The website is rebuilt and published on every push to `main`. To build it
+locally:
+
+```bash
+uv sync --group website
+uv run python website/build.py
+uv run python -m http.server -d website/_build/site    # http://127.0.0.1:8000/
+```
 
 ```
 src/pyweft/           the framework (zero runtime dependencies)
   static/             the browser side: runtime.js, the page shell, the worker
 packages/pyweft-ui/   the control toolkit, released as its own package
-docs/                 the guide
+docs/                 the guide (the website splits it into pages)
 examples/             a headless demo, the todo app and the shop (pages)
+website/              the website: home page, tutorial, build script
 tests/                the framework's tests
 ```
 
@@ -282,9 +302,9 @@ handlers and Web Worker background work; file and confirmation dialogs on
 both targets; the app's title and icon, and window settings; scoped styles
 and CSS framework support; the `pyweft` CLI with hot reload, static builds
 and pre-rendered first screens; `pyweft-ui` with 22 keyboard-accessible
-controls and a gallery.
+controls and a gallery; both released on PyPI.
 
-**Next:** publishing `pyweft` and `pyweft-ui` to PyPI; more controls (menus,
+**Next:** more controls (menus,
 a date picker, form validation); installers (`.msi`, `.dmg`) and code
 signing for desktop apps.
 
@@ -292,4 +312,4 @@ signing for desktop apps.
 
 ## License
 
-MIT. See [LICENSE](LICENSE).
+MIT. See [LICENSE](https://github.com/prassanthn/PyWeft/blob/main/LICENSE).

{pyweft-0.2.0 → pyweft-0.3.0}/docs/getting-started.md

@@ -51,6 +51,8 @@ later mobile: only the transport differs.
    [PyPI packages](#using-pypi-packages),
    [calling JavaScript](#calling-javascript),
    [files and dialogs](#files-and-dialogs),
+   [loading data (http)](#loading-data-pywefthttp),
+   [saving data between visits (storage)](#saving-data-between-visits-pyweftstorage),
    [building for deployment](#building-for-deployment),
    [a desktop app](#a-desktop-app-pyweft-run---desktop),
    [handing it out](#handing-out-a-desktop-app-pyweft-build---desktop)
@@ -62,18 +64,17 @@ later mobile: only the transport differs.
 
 ## 1. Install
 
-PyWeft is not on PyPI yet, so install it straight from GitHub. With uv:
+With uv:
 
 ```bash
 uv init myproject && cd myproject
-uv add git+https://github.com/prassanthn/PyWeft.git
+uv add pyweft
 uv run pyweft new myapp
 uv run pyweft run myapp
 ```
 
-With pip, the equivalent is
-`pip install git+https://github.com/prassanthn/PyWeft.git`, then `pyweft new`
-and `pyweft run` directly.
+With pip, the equivalent is `pip install pyweft`, then `pyweft new` and
+`pyweft run` directly.
 
 To hack on the framework itself, clone it and install in editable mode:
 
@@ -1695,6 +1696,21 @@ page:
 `@apply` works in `_tailwind/input.css`, but not in a component's `<style>`
 block, which Tailwind never reads.
 
+**Classes that depend on state.** A `:class` sets the whole attribute, so
+an element with both `class` and `:class` gets only the `:class` one. Put
+the fixed classes in the expression too:
+
+```xml
+<button @click="show = name"
+        :class="'rounded-lg px-3 py-1.5 ' + ('bg-slate-900 text-white' if name == show else 'text-slate-500')">
+  {{ name }}
+</button>
+```
+
+The todo and shop examples (`examples/todo`, `examples/shop`) are styled
+with Tailwind's CLI exactly as above: see each one's `_tailwind/input.css`
+for the setup and the command that rebuilds its `tailwind.css`.
+
 ### Ready-made controls: pyweft-ui
 
 If you'd rather not write HTML and CSS at all, `pyweft-ui` gives you styled,
@@ -1729,15 +1745,13 @@ reference; and the gallery shows every control live:
 uv run pyweft run packages/pyweft-ui/gallery
 ```
 
-It is not on PyPI yet. Install it from GitHub into the same environment as
-PyWeft:
+Install it into the same environment as PyWeft:
 
 ```bash
-uv add "pyweft-ui @ git+https://github.com/prassanthn/PyWeft.git#subdirectory=packages/pyweft-ui"
+uv add pyweft-ui
 ```
 
-(with pip: `pip install "git+https://github.com/prassanthn/PyWeft.git#subdirectory=packages/pyweft-ui"`),
-then add `"pyweft-ui"` to the `dependencies` in your app's own
+(with pip: `pip install pyweft-ui`), then add `"pyweft-ui"` to the `dependencies` in your app's own
 `pyproject.toml`. PyWeft ships it to the browser for you (see "Components
 from packages"). Inside a clone of this repository, `uv sync` already
 installs it.
@@ -1872,6 +1886,101 @@ async def clear(self):
 - **In tests**, `dialogs.set_host()` installs a stand-in that answers
   instead of the user; without one, the calls raise an error saying so.
 
+### Loading data: pyweft.http
+
+`pyweft.http` calls web APIs and loads files, the same way in the browser
+and in a [desktop app](#a-desktop-app-pyweft-run---desktop). Requests are
+`async`, so make them in `async` handlers or an `async def on_init`:
+
+```python
+from pyweft import http
+
+orders: list = []
+error: str = ""
+
+async def on_init(self):
+    self.orders = await http.get_json("https://api.example.com/orders")
+
+async def save(self, order):
+    response = await http.post("https://api.example.com/orders", json=order)
+    if not response.ok:
+        self.error = f"Couldn't save the order ({response.status})"
+```
+
+| Call | Returns |
+|---|---|
+| `get_json(url)` | the body parsed as JSON; `http.HTTPError` unless the status is 2xx |
+| `get(url)`, `post(url)`, `put(url)`, `patch(url)`, `delete(url)` | a `Response`, whatever its status |
+| `request(method, url)` | the same, for any method |
+
+Each takes `params=` (added to the URL's query), `headers=`, `timeout=`
+(seconds, 30 by default) and a body: `json=` (any JSON value) or `data=`
+(bytes, text, or a dict sent as a form).
+
+- **A `Response`** has `status`, `ok` (a 2xx status), `headers` (names in
+  lower case), `data` (the bytes), `text` and `json()`.
+  `raise_for_status()` raises `http.HTTPError` unless it's 2xx.
+- **A relative URL is a file your app ships.** Put data files in
+  `assets/`, and `await http.get_json("assets/prices.json")` reads them in
+  the browser and in a desktop window alike.
+- **Failures:** no answer at all (offline, a mistyped address) raises
+  `http.NetworkError`; a slow server raises `TimeoutError`.
+- **In the browser, the browser's rules apply.** A request to another site
+  only works if that server allows it (it must send CORS headers; public
+  APIs usually do). There is no such rule in a desktop app.
+- **Everyone can see the requests a web app makes**, as with any web page,
+  so an API key in your code isn't secret. Keep secrets on a server of
+  your own and call that.
+- **In tests**, requests go out for real through the standard library.
+  `http.set_host()` installs a stand-in instead: an object with `async
+  request(method, url, headers, body, timeout)` returning `(status,
+  headers, data, url)`.
+
+### Saving data between visits: pyweft.storage
+
+`pyweft.storage` keeps small amounts of data, such as settings, a draft or
+a list, until the next visit:
+
+```python
+from pyweft import effect, storage
+
+items: list = []
+
+def on_init(self):
+    self.items = storage.get("todos", [])   # [] the first time
+
+@effect
+def keep(self):
+    storage.set("todos", self.items)        # runs again whenever items changes
+```
+
+| Call | Does |
+|---|---|
+| `get(key, default=None)` | the stored value, or `default` |
+| `set(key, value)` | stores `value`, replacing what was there |
+| `delete(key)`, `clear()` | removes one key, or everything this app stored |
+| `has(key)`, `keys()` | whether a key has a value; every key, sorted |
+
+- **Values are anything JSON can hold:** numbers, text, `True`/`False`/
+  `None`, and lists and dicts of those. Anything else raises `TypeError`;
+  turn dates into text first, for example.
+- **`get` returns a copy.** Changing a list you got back doesn't change
+  what's stored until you `set` it again, which is what the effect above
+  does.
+- **The calls aren't `async`**, so they work anywhere: in `on_init`, an
+  effect, a property, or a module of your app.
+- **Where it lives:** in the browser, the browser's local storage for your
+  site (about 5 MB in all, cleared if the visitor clears site data), kept
+  apart per app by the `[project]` name in its `pyproject.toml`. In a
+  desktop app, a JSON file in the user's data folder:
+  `%APPDATA%\<name>\storage.json` on Windows,
+  `~/Library/Application Support/<name>/` on macOS,
+  `~/.local/share/<name>/` on Linux.
+- **Not in `run_in_background`:** the worker can't reach the page's
+  storage, so read what the function needs first and pass it in.
+- **In tests** it lives in memory. `storage.set_host(storage.MemoryStorage())`
+  starts a test empty; `storage.FileStorage(path)` keeps it in a file.
+
 ### Building for deployment
 
 ```bash

{pyweft-0.2.0 → pyweft-0.3.0}/pyproject.toml

@@ -35,7 +35,7 @@ package = ["pywebview>=5", "pyinstaller>=6"]
 
 [project.urls]
 Homepage = "https://github.com/prassanthn/PyWeft"
-Documentation = "https://github.com/prassanthn/PyWeft/blob/main/docs/getting-started.md"
+Documentation = "https://prassanthn.github.io/PyWeft/"
 Issues = "https://github.com/prassanthn/PyWeft/issues"
 
 [project.scripts]
@@ -70,3 +70,11 @@ pyweft-ui = { workspace = true }
 
 [dependency-groups]
 dev = ["pyweft-ui"]
+# The website (website/build.py): uv sync --group website
+# and the examples' Tailwind stylesheets (examples/*/_tailwind/input.css)
+website = [
+    "mkdocs-material>=9.8,<10; python_version >= '3.11'",
+    "pytailwindcss>=0.4; python_version >= '3.11'",
+    # the todo example's own dependency, so its first screen can be pre-rendered
+    "humanize",
+]

{pyweft-0.2.0 → pyweft-0.3.0}/src/pyweft/__init__.py

@@ -4,7 +4,7 @@ Markup in XML, logic in Python, one render core that emits transport-agnostic
 patches so desktop (webview), web (Pyodide) and mobile can share a codebase.
 """
 
-from . import dialogs
+from . import dialogs, http, storage
 from .background import BackgroundError, run_in_background
 from .component import (
     Component,
@@ -24,7 +24,7 @@ from .store import Store
 from .styles import collect_styles, scope_css
 from .vdom import Element, Node, Text, to_dicts
 
-__version__ = "0.2.0"
+__version__ = "0.3.0"
 
 __all__ = [
     "Component",
@@ -43,6 +43,8 @@ __all__ = [
     "Store",
     "set_title",
     "dialogs",
+    "http",
+    "storage",
     "collect_styles",
     "scope_css",
     "diff",

{pyweft-0.2.0 → pyweft-0.3.0}/src/pyweft/cli.py

@@ -234,6 +234,26 @@ def app_identity(app_dir: Path) -> AppIdentity:
     return AppIdentity(title=title.strip(), icon=icon)
 
 
+def app_id(app_dir: Path) -> str:
+    """A stable name for keeping the app's data apart (pyweft.storage): the
+    ``[project]`` name from its pyproject.toml, else the folder's name.
+    Renaming the project starts its saved data afresh."""
+    name = ""
+    pyproject = app_dir / "pyproject.toml"
+    if pyproject.exists():
+        text = pyproject.read_text(encoding="utf-8")
+        if tomllib is not None:
+            try:
+                name = tomllib.loads(text).get("project", {}).get("name", "")
+            except tomllib.TOMLDecodeError as exc:
+                raise CliError(f"{pyproject}: {exc}") from None
+        else:
+            name = _flat_table(text, "project").get("name", "")
+    if not isinstance(name, str) or not name.strip():
+        name = app_dir.resolve().name
+    return re.sub(r"[^a-z0-9._-]+", "-", name.strip().lower()).strip("-.") or "app"
+
+
 # mimetypes reads the Windows registry, which can be wrong or missing these.
 _CONTENT_TYPES = {
     ".css": "text/css",
@@ -515,6 +535,7 @@ def render_shell(
             "__PYWEFT_LIBRARIES__",
             json.dumps([{"name": lib.name, "files": lib.files} for lib in app_libraries(app_dir)]),
         )
+        .replace("__PYWEFT_APP_ID__", json.dumps(app_id(app_dir)))
         .replace("__PYWEFT_DEV__", "true" if dev else "false")
         .replace("__PYWEFT_SINCE__", str(since))
         .replace("__PYWEFT_CSS__", css)