This release is a pre-release and may not be stable for production use.
Ubo GUI
GUI sdk for Ubo Pod
📋 Requirements
📦 Installation
You can install it using this handle: headless-kivy-pi@git+https://github.com/ubopod/ubo-gui.git
# pip:
pip install headless-kivy-pi@git+https://github.com/ubopod/ubo-gui.git
🛠 Usage
Checkout Ubo App to see a sample implementation.
🤝 Contributing
You need to have uv installed on your machine.
To install the required dependencies, run the following command in the root directory of the project:
uv sync
You can run linter over whole codebase by running this command:
uv run poe lint
Subscriptions
The subscriptions are divided into three groups:
- Screen subscriptions are those assigned to a particular stack item, but their handlers doesn't change anything in the
StackItemitself. The handler just changes something on the rendered screen and if that stack item is not visible, the handler doesn't need to be called. Therefore these subscriptions are cleared when the current screen is changed. Samples:itemsof the currently visible menutitleof the currently visible screen
- Menu subscriptions are those assigned to a particular menu. Like screen subscriptions, they are cleared when the current screen is changed. They also get cleared when the menu is scrolled.
Samples:
headingof a headed menusub_headingof a headed menuplaceholderof a menu
- Stack item subscriptions are those assigned to a particular stack item. They are cleared when the stack item is popped. They stay alive as long as the stack item is in the stack, even if it is in the background.
In other words, unlike the other two, they are not cleared when, for example, a sub-menu or an application is opened on top of the current stack item.
Samples:
menuof an item
⚠️ Important Note
Make sure to run uv run poe download_font to download Material Symbols font.
🔒 License
This project is released under the Apache-2.0 License. See the LICENSE file for more details.
Metadata
Release files for ubo-gui 0.13.9.dev1241130103989810153979755
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ubo_gui-0.13.9.dev1241130103989810153979755.tar.gz | 8.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ubo_gui-0.13.9.dev1241130103989810153979755-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.2 MB
Release files / ubo_gui-0.13.9.dev1241130103989810153979755.tar.gz
| Download URL | ubo_gui-0.13.9.dev1241130103989810153979755.tar.gz |
|---|---|
| Size | 8.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b116a5f1b46006b51799cad5c9818029a172cc80ed461c07038e982930e1813f
|
|
BLAKE2b-256 checksum How to use checksums |
86468cdbea6173e8c213e1fbf45103184e7c5e69b7566595d987e0129c90736b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 30, 2024.
Transparency logRelease files / ubo_gui-0.13.9.dev1241130103989810153979755-py3-none-any.whl
| Download URL | ubo_gui-0.13.9.dev1241130103989810153979755-py3-none-any.whl |
|---|---|
| Size | 8.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50ec9719d63f7d8ea87d77df38d012b8461f1be69da4a791d5ba33a6d0c58793
|
|
BLAKE2b-256 checksum How to use checksums |
ed56cb4761a0e05dd03fb2b50062aedfe20ea30265bd2727031c95a2d4dd2835
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 30, 2024.
Transparency log