| Name | textology JSON |
| Version |
0.5.1
JSON |
| download |
| home_page | None |
| Summary | Textual extensions for creating Terminal User Interfaces |
| upload_time | 2024-03-31 21:43:04 |
| maintainer | None |
| docs_url | None |
| author | David Fritz |
| requires_python | >=3.10 |
| license | MIT |
| keywords |
cli
tui
widgets
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
textual
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<div align="center">
<img src="https://raw.githubusercontent.com/pyranha-labs/textology/main/docs/banner.svg" width="450">
</div>
-----------------
[](https://docs.python.org/3.10/)
[](https://devguide.python.org/versions)
[](https://google.github.io/styleguide/pyguide.html)
[](https://github.com/PyCQA/isort)
[](https://github.com/psf/black)
[](https://github.com/PyCQA/pycodestyle)
[](https://github.com/PyCQA/pydocstyle)
[](https://github.com/python/mypy)
[](https://github.com/PyCQA/pylint)
[](https://github.com/pytest-dev/pytest)
[](https://github.com/PyCQA/bandit)
[](LICENSE)
# Textology
### The study of making interactive UIs with text.
Why should GUIs have all the fun? Textology extends the amazing functionality of
[Textual](https://github.com/Textualize/textual) and [Rich](https://github.com/Textualize/rich),
to help create TUIs with popular UI design patterns and principals from web and mobile frameworks.
Refer to [Top Features](#top-features) for a summary of the extensions provided.
#### Additional Background
Commonly known as Text (or Terminal) User Interfaces, the goal of a TUI (Tooey) is to provide as close
as possible to a traditional GUI experience straight from a terminal. Why? Not all environments allow full graphical
library access, web access, etc., but almost all provide access from a terminal. Yes, even terminals can provide
mouse support, sophisticated layouts, animations, and a wide range of colors!
Like Textual, Textology is inspired by modern web development. Textology extends Textual by bringing together, and
expanding upon, designs from other frameworks such as Dash/FastAPI/Flask, including their use of routing, annotations,
and observation patterns. Why? To increase developer velocity based on existing experience. Textology also receives
inspiration from other UI frameworks external to Python, such as iOS, Android, and Web frameworks. Most importantly
however, Textology is an extension of Textual: it does not replace Textual, but rather provides additional options
on top of the core Textual framework.
Before using Textology, be comfortable with Textual. For tutorials, guides, etc., refer to the
[Textual Documentation](https://textual.textualize.io/guide/). Textology is NOT a replacement for Textual, it is an
extension. Callbacks, widgets, screens, event lifecycles, etc., from Textual still apply to Textology extended
widgets and applications. For other advanced features, familiarity with Dash/FastAPI/Flask principles will help.
Examples for Textology extensions, such as callback based applications, are included in this documentation.
## Table Of Contents
* [Top Features](#top-features)
* [Compatibility](#compatibility)
* [Getting Started](#getting-started)
* [Installation](#installation)
* [Extended Applications](#extended-applications)
* [Extended Widgets](#extended-widgets)
* [Extended Testing](#extended-testing)
## Top Features
- Multiple theme support
- Swap CSS themes live
- Apply multiple CSS themes simultaneously
- Extended callbacks
- Declare Widget callbacks/event handling without subclassing
- Declare Apps with "event driven architecture/observation pattern" to detect changes and automatically update UI
- Listen to reactive attribute changes.
- Listen to events/messages/errors.
- Extended native widgets, including (but not limited to):
- All widgets: ability to disable event messages and declare styles without subclassing
- ListItems with data objects
- Buttons with automatic tracking of click counts
- New widgets, including (but not limited to):
- ListItemHeaders (non-interactive ListItems)
- HorizontalMenus (walkable list of ListViews with peeking at following lists)
- MultiSelect (dropdown list with ability to select multiple items).
- Enhanced testing support
- Parallel tests via python-xdist
- Custom testing arguments, such as updating snapshots on failures
## Compatibility
Textology follows [Textual Compatibility](https://github.com/Textualize/textual#compatibility) guidelines with one
exception: Python3.10 minimum requirement.
## Getting Started
### Installation
Install Textology via pip:
```shell
pip install textology
```
For development of applications based on Textual/Textology (but not development of Textology itself), use the
`[dev]` package. This installs extra Textual development tools, and requirements for Textology testing extensions.
```shell
pip install textology[dev]
```
For full development of Textology itself, refer to [Contributing](CONTRIBUTING.md). This installs Textual development tools,
requirements for Textology testing extensions, and full QA requirements to meet commit standards. This version
has the highest library requirements, in order to match the versions used by Textology itself for testing. Required if
developing Textology itself, or recommended if looking to match/exceed the level of QA testing used by Textology.
### Extended Widgets
Native Textual widgets can be directly swapped out with Textology extended equivalents. They can then be used as is
(standard Textual usage), or with extensions (via extra keyword arguments).
- Basic swap (no extensions):
```python
# Replace:
from textual.widgets import Button
# With:
from textology.widgets import Button
```
- Instance callback extension (avoid global watchers, name/ID checks in the event watchers, and event chaining):
```python
from textology.widgets import Button
button = Button(
callbacks={"on_button_pressed": lambda event: print("Don't press my buttons...")},
)
```
- Instance style extension (set styles directly at instantiation based on logic):
```python
from textology.widgets import Button
feeling_blue = True
button = Button(
styles={
"background": "blue" if feeling_blue else "green",
},
)
```
- Instance message disable extension (avoid unused event chains, such as in large ListViews):
```python
from textual import events
from textology.widgets import ListItem
item = ListItem(
disabled_messages=[events.Mount, events.Show],
)
```
### Extended Applications
Textology App classes, such as `WidgetApp`, can replace any regular Textual App, and be used as is without any
extensions turned on. Here are examples of the most commonly used application subclasses, `WidgetApp` and
`ExtendedApp`, and their primary extended functionality being used. More detailed examples of applications based
around routes, callbacks, and standard Textual applications can be found in [Examples](https://github.com/pyranha-labs/textology/examples).
- Basic App without subclassing:
```python
from textology.apps import WidgetApp
from textology.widgets import Button, Container, Label
app = WidgetApp(
Container(
Button("Ping", callbacks={
"on_button_pressed": lambda event: app.query_one('#label').update("Ping")
}),
Button("Pong", callbacks={
"on_button_pressed": lambda event: app.query_one('#label').update("Pong")
}),
Button("Sing-a-long", callbacks={
"on_button_pressed": lambda event: app.query_one('#label').update("Sing-a-long")
}),
Label(id="label")
)
)
app.run()
```
- Observer/callback application (automatic attribute monitoring and updates by element IDs without manual queries):
```python
from textology.apps import ExtendedApp
from textology.observers import Modified, Select, Update
from textology.widgets import Button, Container, Label
app = ExtendedApp(
child=Container(
Button("Ping", id="ping-btn"),
Button("Pong", id="pong-btn"),
Button("Sing-a-long", id="sing-btn"),
Container(
id="content",
),
)
)
@app.when(
Modified("ping-btn", "n_clicks"),
Update("content", "children"),
)
def ping(clicks):
return Label(f"Ping pressed {clicks}")
@app.when(
Modified("pong-btn", "n_clicks"),
Update("content", "children"),
)
def pong(clicks):
return Label(f"Pong pressed {clicks}")
@app.when(
Modified("sing-btn", "n_clicks"),
Select("ping-btn", "n_clicks"),
Select("pong-btn", "n_clicks"),
Update("content", "children"),
)
def song(song_clicks, ping_clicks, pong_clicks):
if not ping_clicks or not pong_clicks:
return Label(f"Press Ping and Pong first to complete the song!")
return Label(f"Ping, pong, sing-a-long song pressed {song_clicks}")
app.run()
```
- Callbacks can also be async:
```python
@app.when(
Modified("pong-btn", "n_clicks"),
Update("content", "children"),
)
async def delayed_pong(clicks):
await asyncio.sleep(3)
return Label(f"Pong pressed {clicks} and updated 3 seconds later")
```
- Callbacks can also catch Exceptions from other callbacks:
```python
@app.when(
Raised(Exception),
)
def error_notification(error):
app.notify(f"An unknown error occurred: {error}", title="Error")
```
- <details>
<summary>Callbacks can also listen for stateless events, not just stateful attribute updates</summary>
```python
from textology.apps import ExtendedApp
from textology.observers import Published, Select, Update
from textology.widgets import Button, Container, Label
app = ExtendedApp(
child=Container(
Button("Ping", id="ping-btn"),
Button("Pong", id="pong-btn"),
Button("Sing-a-long", id="sing-btn"),
Container(
id="content",
),
)
)
@app.when(
Published("ping-btn", Button.Pressed),
Update("content", "children"),
)
def ping(event):
return Label(f"Ping pressed {event.button.n_clicks}")
@app.when(
Published("pong-btn", Button.Pressed),
Update("content", "children"),
)
def pong(event):
return Label(f"Pong pressed {event.button.n_clicks}")
@app.when(
Published("sing-btn", Button.Pressed),
Select("ping-btn", "n_clicks"),
Select("pong-btn", "n_clicks"),
Update("content", "children"),
)
def song(event, ping_clicks, pong_clicks):
if not ping_clicks or not pong_clicks:
return Label(f"Press Ping and Pong first to complete the song!")
return Label(f"Ping, pong, sing-a-long song pressed {event.button.n_clicks}")
app.run()
```
- <details>
<summary>Callbacks can also be registered on methods, to share across all application instances</summary>
```python
from textology.apps import ExtendedApp
from textology.observers import Published, Select, Update, when
from textology.widgets import Button, Container, Label
class Page(Container):
def compose(self):
yield Button("Ping", id="ping-btn")
yield Button("Pong", id="pong-btn")
yield Button("Sing-a-long", id="sing-btn")
yield Container(
id="content",
)
@when(
Published("ping-btn", Button.Pressed),
Update("content", "children"),
)
def ping(self, event):
return Label(f"Ping pressed {event.button.n_clicks}")
@when(
Published("pong-btn", Button.Pressed),
Update("content", "children"),
)
def pong(self, event):
return Label(f"Pong pressed {event.button.n_clicks}")
@when(
Published("sing-btn", Button.Pressed),
Select("ping-btn", "n_clicks"),
Select("pong-btn", "n_clicks"),
Update("content", "children"),
)
def song(self, event, ping_clicks, pong_clicks):
if not ping_clicks or not pong_clicks:
return Label(f"Press Ping and Pong first to complete the song!")
return Label(f"Ping, pong, sing-a-long song pressed {event.button.n_clicks}")
app = ExtendedApp(
child=Page()
)
app.run()
```
- <details>
<summary>Callbacks can also use Dash code style (Same as others, but with Dash compatibility object and calls)</summary>
```python
from textology.dash_compat import DashCompatApp, Input, Output, State
from textology.widgets import Button, Container, Label
app = DashCompatApp(
layout=Container(
Button("Ping", id="ping-btn"),
Button("Pong", id="pong-btn"),
Button("Sing-a-long", id="sing-btn"),
Container(
id="content",
),
)
)
@app.callback(
Input("ping-btn", "n_clicks"),
Output("content", "children"),
)
def ping(clicks):
return Label(f"Ping pressed {clicks}")
@app.callback(
Input("pong-btn", "n_clicks"),
Output("content", "children"),
)
def pong(clicks):
return Label(f"Pong pressed {clicks}")
@app.callback(
Input("sing-btn", "n_clicks"),
State("ping-btn", "n_clicks"),
State("pong-btn", "n_clicks"),
Output("content", "children"),
)
def song(song_clicks, ping_clicks, pong_clicks):
if not ping_clicks or not pong_clicks:
return Label(f"Press Ping and Pong first to complete the song!")
return Label(f"Ping, pong, sing-a-long song pressed {song_clicks}")
app.run()
```
### Extended Testing
Don't want to serialize your pytests? Looking for the ability to quickly visualize differences when UIs change?
You came to the right place. Textology extends Textual SVG snapshot capabilities to add support for parallel processing
during tests (python-xdist), and custom options such as auto updating SVG snapshots on failures. In order to use the
pytest extensions automagically, add the following to a `conftest.py` in the root of the project. This will enable
usage of the `compare_snapshots` fixture, and HTML report generation on failure, automatically.
```python
pytest_plugins = ("textology.pytest_utils",)
```
- Basic snapshot test:
```python
import pytest
from textual import App
from textual.widgets import Button
class BasicApp(App):
def compose(self):
yield Button("Click me!")
@pytest.mark.asyncio
async def test_snapshot_with_app(compare_snapshots):
assert await compare_snapshots(BasicApp())
```
Other advanced testing features include:
- Ability to pass an App, App Pilot, or a module containing an instantiated App or Pilot, to fixtures
- Custom snapshot paths, including reusing the same snapshot across multiple tests
- Automatic SVG updates with `pytest --txtology-snap-update`
View all options by running `pytest -h` and referring to `Custom options:` section.
Raw data
{
"_id": null,
"home_page": null,
"name": "textology",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": "cli, tui, widgets",
"author": "David Fritz",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/b6/b9/d89320c85cfbc8511e12c1e6799c85ed66cc8d0bd08629e46d1ee0211395/textology-0.5.1.tar.gz",
"platform": "MacOS",
"description": "\n<div align=\"center\">\n <img src=\"https://raw.githubusercontent.com/pyranha-labs/textology/main/docs/banner.svg\" width=\"450\">\n</div>\n\n-----------------\n\n\n[](https://docs.python.org/3.10/)\n[](https://devguide.python.org/versions)\n[](https://google.github.io/styleguide/pyguide.html)\n[](https://github.com/PyCQA/isort)\n[](https://github.com/psf/black)\n[](https://github.com/PyCQA/pycodestyle)\n[](https://github.com/PyCQA/pydocstyle)\n[](https://github.com/python/mypy)\n[](https://github.com/PyCQA/pylint)\n[](https://github.com/pytest-dev/pytest)\n[](https://github.com/PyCQA/bandit)\n[](LICENSE)\n\n\n# Textology\n\n### The study of making interactive UIs with text.\n\nWhy should GUIs have all the fun? Textology extends the amazing functionality of\n[Textual](https://github.com/Textualize/textual) and [Rich](https://github.com/Textualize/rich),\nto help create TUIs with popular UI design patterns and principals from web and mobile frameworks.\nRefer to [Top Features](#top-features) for a summary of the extensions provided.\n\n#### Additional Background\n\nCommonly known as Text (or Terminal) User Interfaces, the goal of a TUI (Tooey) is to provide as close\nas possible to a traditional GUI experience straight from a terminal. Why? Not all environments allow full graphical\nlibrary access, web access, etc., but almost all provide access from a terminal. Yes, even terminals can provide\nmouse support, sophisticated layouts, animations, and a wide range of colors!\n\nLike Textual, Textology is inspired by modern web development. Textology extends Textual by bringing together, and\nexpanding upon, designs from other frameworks such as Dash/FastAPI/Flask, including their use of routing, annotations,\nand observation patterns. Why? To increase developer velocity based on existing experience. Textology also receives\ninspiration from other UI frameworks external to Python, such as iOS, Android, and Web frameworks. Most importantly\nhowever, Textology is an extension of Textual: it does not replace Textual, but rather provides additional options\non top of the core Textual framework.\n\nBefore using Textology, be comfortable with Textual. For tutorials, guides, etc., refer to the\n[Textual Documentation](https://textual.textualize.io/guide/). Textology is NOT a replacement for Textual, it is an\nextension. Callbacks, widgets, screens, event lifecycles, etc., from Textual still apply to Textology extended\nwidgets and applications. For other advanced features, familiarity with Dash/FastAPI/Flask principles will help.\nExamples for Textology extensions, such as callback based applications, are included in this documentation.\n\n\n## Table Of Contents\n\n * [Top Features](#top-features)\n * [Compatibility](#compatibility)\n * [Getting Started](#getting-started)\n * [Installation](#installation)\n * [Extended Applications](#extended-applications)\n * [Extended Widgets](#extended-widgets)\n * [Extended Testing](#extended-testing)\n\n\n## Top Features\n\n- Multiple theme support\n - Swap CSS themes live\n - Apply multiple CSS themes simultaneously\n- Extended callbacks\n - Declare Widget callbacks/event handling without subclassing\n - Declare Apps with \"event driven architecture/observation pattern\" to detect changes and automatically update UI\n - Listen to reactive attribute changes.\n - Listen to events/messages/errors.\n- Extended native widgets, including (but not limited to):\n - All widgets: ability to disable event messages and declare styles without subclassing\n - ListItems with data objects\n - Buttons with automatic tracking of click counts\n- New widgets, including (but not limited to):\n - ListItemHeaders (non-interactive ListItems)\n - HorizontalMenus (walkable list of ListViews with peeking at following lists)\n - MultiSelect (dropdown list with ability to select multiple items).\n- Enhanced testing support\n - Parallel tests via python-xdist\n - Custom testing arguments, such as updating snapshots on failures\n\n\n## Compatibility\n\nTextology follows [Textual Compatibility](https://github.com/Textualize/textual#compatibility) guidelines with one\nexception: Python3.10 minimum requirement.\n\n\n## Getting Started\n\n### Installation\n\nInstall Textology via pip:\n```shell\npip install textology\n```\n\nFor development of applications based on Textual/Textology (but not development of Textology itself), use the\n`[dev]` package. This installs extra Textual development tools, and requirements for Textology testing extensions.\n```shell\npip install textology[dev]\n```\n\nFor full development of Textology itself, refer to [Contributing](CONTRIBUTING.md). This installs Textual development tools,\nrequirements for Textology testing extensions, and full QA requirements to meet commit standards. This version\nhas the highest library requirements, in order to match the versions used by Textology itself for testing. Required if\ndeveloping Textology itself, or recommended if looking to match/exceed the level of QA testing used by Textology.\n\n### Extended Widgets\n\nNative Textual widgets can be directly swapped out with Textology extended equivalents. They can then be used as is\n(standard Textual usage), or with extensions (via extra keyword arguments).\n\n- Basic swap (no extensions):\n```python\n# Replace:\nfrom textual.widgets import Button\n\n# With:\nfrom textology.widgets import Button\n```\n\n- Instance callback extension (avoid global watchers, name/ID checks in the event watchers, and event chaining):\n```python\nfrom textology.widgets import Button\n\nbutton = Button(\n callbacks={\"on_button_pressed\": lambda event: print(\"Don't press my buttons...\")},\n)\n```\n\n- Instance style extension (set styles directly at instantiation based on logic):\n```python\nfrom textology.widgets import Button\n\nfeeling_blue = True\n\nbutton = Button(\n styles={\n \"background\": \"blue\" if feeling_blue else \"green\",\n },\n)\n```\n\n- Instance message disable extension (avoid unused event chains, such as in large ListViews):\n```python\nfrom textual import events\nfrom textology.widgets import ListItem\n\nitem = ListItem(\n disabled_messages=[events.Mount, events.Show],\n)\n```\n\n### Extended Applications\n\nTextology App classes, such as `WidgetApp`, can replace any regular Textual App, and be used as is without any\nextensions turned on. Here are examples of the most commonly used application subclasses, `WidgetApp` and\n`ExtendedApp`, and their primary extended functionality being used. More detailed examples of applications based\naround routes, callbacks, and standard Textual applications can be found in [Examples](https://github.com/pyranha-labs/textology/examples).\n\n- Basic App without subclassing:\n\n ```python\n from textology.apps import WidgetApp\n from textology.widgets import Button, Container, Label\n \n app = WidgetApp(\n Container(\n Button(\"Ping\", callbacks={\n \"on_button_pressed\": lambda event: app.query_one('#label').update(\"Ping\")\n }),\n Button(\"Pong\", callbacks={\n \"on_button_pressed\": lambda event: app.query_one('#label').update(\"Pong\")\n }),\n Button(\"Sing-a-long\", callbacks={\n \"on_button_pressed\": lambda event: app.query_one('#label').update(\"Sing-a-long\")\n }),\n Label(id=\"label\")\n )\n )\n app.run()\n ```\n\n- Observer/callback application (automatic attribute monitoring and updates by element IDs without manual queries):\n\n ```python\n from textology.apps import ExtendedApp\n from textology.observers import Modified, Select, Update\n from textology.widgets import Button, Container, Label\n \n app = ExtendedApp(\n child=Container(\n Button(\"Ping\", id=\"ping-btn\"),\n Button(\"Pong\", id=\"pong-btn\"),\n Button(\"Sing-a-long\", id=\"sing-btn\"),\n Container(\n id=\"content\",\n ),\n )\n )\n \n @app.when(\n Modified(\"ping-btn\", \"n_clicks\"),\n Update(\"content\", \"children\"),\n )\n def ping(clicks):\n return Label(f\"Ping pressed {clicks}\")\n \n @app.when(\n Modified(\"pong-btn\", \"n_clicks\"),\n Update(\"content\", \"children\"),\n )\n def pong(clicks):\n return Label(f\"Pong pressed {clicks}\")\n \n @app.when(\n Modified(\"sing-btn\", \"n_clicks\"),\n Select(\"ping-btn\", \"n_clicks\"),\n Select(\"pong-btn\", \"n_clicks\"),\n Update(\"content\", \"children\"),\n )\n def song(song_clicks, ping_clicks, pong_clicks):\n if not ping_clicks or not pong_clicks:\n return Label(f\"Press Ping and Pong first to complete the song!\")\n return Label(f\"Ping, pong, sing-a-long song pressed {song_clicks}\")\n \n app.run()\n ```\n\n- Callbacks can also be async:\n ```python\n @app.when(\n Modified(\"pong-btn\", \"n_clicks\"),\n Update(\"content\", \"children\"),\n )\n async def delayed_pong(clicks):\n await asyncio.sleep(3)\n return Label(f\"Pong pressed {clicks} and updated 3 seconds later\")\n ```\n\n\n- Callbacks can also catch Exceptions from other callbacks:\n ```python\n @app.when(\n Raised(Exception),\n )\n def error_notification(error):\n app.notify(f\"An unknown error occurred: {error}\", title=\"Error\")\n ```\n\n- <details>\n <summary>Callbacks can also listen for stateless events, not just stateful attribute updates</summary>\n\n ```python\n from textology.apps import ExtendedApp\n from textology.observers import Published, Select, Update\n from textology.widgets import Button, Container, Label\n \n app = ExtendedApp(\n child=Container(\n Button(\"Ping\", id=\"ping-btn\"),\n Button(\"Pong\", id=\"pong-btn\"),\n Button(\"Sing-a-long\", id=\"sing-btn\"),\n Container(\n id=\"content\",\n ),\n )\n )\n \n @app.when(\n Published(\"ping-btn\", Button.Pressed),\n Update(\"content\", \"children\"),\n )\n def ping(event):\n return Label(f\"Ping pressed {event.button.n_clicks}\")\n \n @app.when(\n Published(\"pong-btn\", Button.Pressed),\n Update(\"content\", \"children\"),\n )\n def pong(event):\n return Label(f\"Pong pressed {event.button.n_clicks}\")\n \n @app.when(\n Published(\"sing-btn\", Button.Pressed),\n Select(\"ping-btn\", \"n_clicks\"),\n Select(\"pong-btn\", \"n_clicks\"),\n Update(\"content\", \"children\"),\n )\n def song(event, ping_clicks, pong_clicks):\n if not ping_clicks or not pong_clicks:\n return Label(f\"Press Ping and Pong first to complete the song!\")\n return Label(f\"Ping, pong, sing-a-long song pressed {event.button.n_clicks}\")\n \n app.run()\n ```\n\n- <details>\n <summary>Callbacks can also be registered on methods, to share across all application instances</summary>\n\n ```python\n from textology.apps import ExtendedApp\n from textology.observers import Published, Select, Update, when\n from textology.widgets import Button, Container, Label\n \n class Page(Container):\n def compose(self):\n yield Button(\"Ping\", id=\"ping-btn\")\n yield Button(\"Pong\", id=\"pong-btn\")\n yield Button(\"Sing-a-long\", id=\"sing-btn\")\n yield Container(\n id=\"content\",\n )\n \n @when(\n Published(\"ping-btn\", Button.Pressed),\n Update(\"content\", \"children\"),\n )\n def ping(self, event):\n return Label(f\"Ping pressed {event.button.n_clicks}\")\n \n @when(\n Published(\"pong-btn\", Button.Pressed),\n Update(\"content\", \"children\"),\n )\n def pong(self, event):\n return Label(f\"Pong pressed {event.button.n_clicks}\")\n \n @when(\n Published(\"sing-btn\", Button.Pressed),\n Select(\"ping-btn\", \"n_clicks\"),\n Select(\"pong-btn\", \"n_clicks\"),\n Update(\"content\", \"children\"),\n )\n def song(self, event, ping_clicks, pong_clicks):\n if not ping_clicks or not pong_clicks:\n return Label(f\"Press Ping and Pong first to complete the song!\")\n return Label(f\"Ping, pong, sing-a-long song pressed {event.button.n_clicks}\")\n \n app = ExtendedApp(\n child=Page()\n )\n \n app.run()\n ```\n\n- <details>\n <summary>Callbacks can also use Dash code style (Same as others, but with Dash compatibility object and calls)</summary>\n\n ```python\n from textology.dash_compat import DashCompatApp, Input, Output, State\n from textology.widgets import Button, Container, Label\n \n app = DashCompatApp(\n layout=Container(\n Button(\"Ping\", id=\"ping-btn\"),\n Button(\"Pong\", id=\"pong-btn\"),\n Button(\"Sing-a-long\", id=\"sing-btn\"),\n Container(\n id=\"content\",\n ),\n )\n )\n \n @app.callback(\n Input(\"ping-btn\", \"n_clicks\"),\n Output(\"content\", \"children\"),\n )\n def ping(clicks):\n return Label(f\"Ping pressed {clicks}\")\n \n @app.callback(\n Input(\"pong-btn\", \"n_clicks\"),\n Output(\"content\", \"children\"),\n )\n def pong(clicks):\n return Label(f\"Pong pressed {clicks}\")\n \n @app.callback(\n Input(\"sing-btn\", \"n_clicks\"),\n State(\"ping-btn\", \"n_clicks\"),\n State(\"pong-btn\", \"n_clicks\"),\n Output(\"content\", \"children\"),\n )\n def song(song_clicks, ping_clicks, pong_clicks):\n if not ping_clicks or not pong_clicks:\n return Label(f\"Press Ping and Pong first to complete the song!\")\n return Label(f\"Ping, pong, sing-a-long song pressed {song_clicks}\")\n \n app.run()\n ```\n\n### Extended Testing\n\nDon't want to serialize your pytests? Looking for the ability to quickly visualize differences when UIs change?\nYou came to the right place. Textology extends Textual SVG snapshot capabilities to add support for parallel processing\nduring tests (python-xdist), and custom options such as auto updating SVG snapshots on failures. In order to use the\npytest extensions automagically, add the following to a `conftest.py` in the root of the project. This will enable\nusage of the `compare_snapshots` fixture, and HTML report generation on failure, automatically.\n\n```python\npytest_plugins = (\"textology.pytest_utils\",)\n```\n\n- Basic snapshot test:\n ```python\n import pytest\n from textual import App\n from textual.widgets import Button\n \n class BasicApp(App):\n def compose(self):\n yield Button(\"Click me!\")\n \n @pytest.mark.asyncio\n async def test_snapshot_with_app(compare_snapshots):\n assert await compare_snapshots(BasicApp())\n ```\n\nOther advanced testing features include:\n- Ability to pass an App, App Pilot, or a module containing an instantiated App or Pilot, to fixtures\n- Custom snapshot paths, including reusing the same snapshot across multiple tests\n- Automatic SVG updates with `pytest --txtology-snap-update`\n\nView all options by running `pytest -h` and referring to `Custom options:` section.\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Textual extensions for creating Terminal User Interfaces",
"version": "0.5.1",
"project_urls": {
"Changelog": "https://github.com/pyranha-labs/textology/releases",
"Home": "https://github.com/pyranha-labs/textology",
"Issues": "https://github.com/pyranha-labs/textology/issues"
},
"split_keywords": [
"cli",
" tui",
" widgets"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "5beaf787add12b66d37f0c4a9b92ce72c829ed6ad6d84c0e5119449c2c2cba97",
"md5": "3531fd243715350645037ed752a2375e",
"sha256": "836e74b887a1f902e57680a796749dce641770a16b4b935e1f2fc4e20ad65fb2"
},
"downloads": -1,
"filename": "textology-0.5.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "3531fd243715350645037ed752a2375e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 99292,
"upload_time": "2024-03-31T21:43:02",
"upload_time_iso_8601": "2024-03-31T21:43:02.409719Z",
"url": "https://files.pythonhosted.org/packages/5b/ea/f787add12b66d37f0c4a9b92ce72c829ed6ad6d84c0e5119449c2c2cba97/textology-0.5.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "b6b9d89320c85cfbc8511e12c1e6799c85ed66cc8d0bd08629e46d1ee0211395",
"md5": "5f2c045db9b423718cbde2b496db6cc6",
"sha256": "e5591faf8375a0420f111041e2691d704ff072f1ba9cef8b6112f3f5b7433cf4"
},
"downloads": -1,
"filename": "textology-0.5.1.tar.gz",
"has_sig": false,
"md5_digest": "5f2c045db9b423718cbde2b496db6cc6",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 74948,
"upload_time": "2024-03-31T21:43:04",
"upload_time_iso_8601": "2024-03-31T21:43:04.059740Z",
"url": "https://files.pythonhosted.org/packages/b6/b9/d89320c85cfbc8511e12c1e6799c85ed66cc8d0bd08629e46d1ee0211395/textology-0.5.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-31 21:43:04",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "pyranha-labs",
"github_project": "textology",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"requirements": [
{
"name": "textual",
"specs": [
[
">=",
"0.51.0"
]
]
}
],
"lcname": "textology"
}
