Turbo-Lazy
Basically, it comes down to the following statement:
{% lazy 'apps.core.partial_views._machine_card' poll_status.machine_id %}
{% include 'core/partials/_machine_card_loading.html' with name=poll_status.name machine_id=poll_status.machine_id %}
{% endlazy %}
The content inside the lazy tag is rendered right away in a turbo-frame with a src tag that points to an auto generated URL where the view given lazy controller is called (with the parameters given in the controller). So this can be a slow loading view as its lazy loaded. This is based on turbo-frames, i.e. the lazy loading is client initiated. With something like turbo-streams (and the django implementation), it would be possible to push the update from the server which would be even cooler (especially a single channel could be used for multiple elements). So, the page will be rendered as follows:
<turbo-frame id="1c87a216-6ad5-4320-861e-261caf3e5dd7" src="/lazy/?token=eyJpZCI6ICIxYzg3YTIxNi02YWQ1LTQzMjAtODYxZS0yNjFjYWYzZTVkZDciLCAidmlldyI6ICJhcHBzLmNvcmUucGFydGlhbF92aWV3cy5fbWFjaGluZV9jYXJkIiwgImFyZ3MiOiBbMV0sICJrd2FyZ3MiOiB7fX0=">
<div class="card bg-primary text-white mb-4">
<div class="card-body">
<b>Machine 1</b>
</div>
<div class="card-footer" style="height: 7rem;">
<div class="d-flex justify-content-center">
<div class="spinner-border" role="status">
<span class="sr-only">Loading...</span>
</div>
</div>
</div>
<div class="card-footer d-flex align-items-center justify-content-between">
<a class="small text-white stretched-link"
href="/machine/1/" target="_top">View Details</a>
<div class="small text-white"><i class="fas fa-angle-right"></i></div>
</div>
</div>
</turbo-frame>
And a call to /lazy/?token=... will return the response of calling the view function
apps.core.partial_views._machine_card with given positional argument poll_status.machine_id also wrapped inside
a <turbo-frame> tag with the same id so that it will automatically swapped by turboframe.
Example
A complete example can be found under example/django_example.
Go to this directory and proceed.
Optionally, create a custom virtualenv
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt
If you want to use the current snapshot of turbo-lazyinstall it via
pip install ../../
Then start everything via
python manage.py migrate
python manage.py runserver
and go to
http://localhost:8000/
Release Notes
0.2.2
- The install dependency
django-tag-parser>=3.2was missing insetup.py
0.2.1
- Template folder was accidentally named wrong in the published version
0.2.0
- Package renamed to 'turbo_lazy' and also root folder renamed to 'turbo_lazy'.
- Template Tag
{% include_view %}was added to integrate complete views into templates (in modulepartials)
0.1.2
- Complete working Django Example
0.1.1
- Several minor fixes
0.1.0
- Initial Release
Metadata
Release files for turbo-lazy 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| turbo_lazy-0.2.2.tar.gz | 8.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| turbo_lazy-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.0 kB
Release files / turbo_lazy-0.2.2.tar.gz
| Download URL | turbo_lazy-0.2.2.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1fb31def479ccc50811be54ae1f6719576f1004f0f3ffbe2d9c5c200804dae67
|
|
BLAKE2b-256 checksum How to use checksums |
ca8096764f4d6aca846fa944306e045927508152f75e12d49c84c58ec9736966
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.6
|
Release files / turbo_lazy-0.2.2-py3-none-any.whl
| Download URL | turbo_lazy-0.2.2-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad7a4081f58a1277524e45c72fb342d4ceda5e0642fde641284711d988e5261a
|
|
BLAKE2b-256 checksum How to use checksums |
26fa7ddeb8ea10182027600625ffef0d0bc34ac6c296fa9e6e14e2d5d02dfa4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.6
|
Security for turbo-lazy 0.2.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.