django-htmx
wasm-service
django-htmx | wasm-service | |
---|---|---|
18 | 11 | |
1,404 | 671 | |
- | - | |
8.6 | 3.8 | |
10 days ago | 3 months ago | |
JavaScript | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-htmx
- Django + Htmx package for simple integration
-
Disabling HTMX Urls
If you don't already, you should use django-htmx. This will allow you to check if the request was made with HTMX. You can then do something like this:
-
HTMX and Wagtail
To make things easier, install the django-htmx package. Then, in your Page model's serve(), you can do things like if request.htmx: and return an HTML snippet instead of the full page in that case.
-
Htmx
The great thing about HTMX is it fits really nicely with templated server-rendered frameworks like Django.
You can have a page with a list of items. The page is one template, and it includes a sub-template which is just the
- items. Then you have a separate view for "get list fragment" which just returns the updated/sorted/filtered
- . If you toggle the ordering, or filter the list, HTMX will automatically call the fragment renderer and replace just the
- items, without reloading the page.
See this example: https://github.com/adamchainz/django-htmx/blob/8054f049f53f0...
This approach solves the common interactivity use-cases requiring JS in a server-rendered app, without having to write any JS, and without having to build a REST API. Instead you just render HTML, which your framework is excellent at.
-
Building a fullstack app with Flask and HTMx
If you use django-htmx, it's pretty simple to get the "this HTTP request came from HTMX" flag and branch accordingly in your view. The docs give a simple example of the logic here:
https://django-htmx.readthedocs.io/en/latest/middleware.html...
The examples give a fleshed-out version: https://github.com/adamchainz/django-htmx/blob/main/example/...
Though that's very slightly different than how I described it above, but it's basically the same idea; in this case you commonize the `main` block between the two contexts.
-
Django Contrib Messages + HTMX ?
HTMX has a HX-Trigger response header that enables you to trigger events in the browser that Javascript code can listen for. Assuming you already have Django-HTMX library set up, you could write a middleware like this:
-
What are your favorite 3rd party packages that you often use with Django?
Nice. I've written some less complete, less consistent variant of this a couple times now. That alone may be worth taking the dependency.
-
Is HTMX a Django-supported equivalent of Rails Hotwire / Turbo?
Full URL for django-htmx: https://github.com/adamchainz/django-htmx (creator here)
-
Frontend with Django
I think it's fair to clarify that Adam Johnson (aka adamchainz on Reddit and GitHub) didn't create HTMX but did write the django-htmx app to make it easier to use HTMX in Django.
-
Django and hx-delete request verb
django-htmx also comes with it's own version of HttpResponseHtmxRedirect (called HttpResponseClientRedirect).
wasm-service
-
Wasm and golang
There is a rust one here: https://github.com/richardanaya/wasm-service
-
Htmx
Check out the live demo! https://richardanaya.github.io/wasm-service/
Last month I contributed the todos functionality to this project.
I think this is a great idea and could eventually enable htmx projects to transition from server-side-only to being a PWA with very little code changes (given the right backend).
Unfortunately this particular implementation exhibits some blocking issues which I was not able to solve yet:
1. The Service Worker is eventually unloaded from memory, which means all data is lost because it currently stores everything in memory. This isn't a defect as much as it is lacking a persistence feature; this is a MVP (emphasis on minimal) after all. The most promising solution in my opinion would be to use the OPFS/File System Access API with SQLite, which is yet to be shipped in all browsers.
2. The bigger issue is that once the SW is unloaded it doesn't come back. The SW getting reaped after being idle is fine, that's part of the expected behavior. But there are no events or any other indication that it was disconnected, at some point it just stops intercepting requests. I don't know why. If anyone can chip in here to say why it does this and how I can detect or somehow restart SW fetch interception on demand I would be glad to hear it.
( For some more detail see the "# Remaining Issues" in my PR #5: https://github.com/richardanaya/wasm-service/pull/5 )
- Serve local and remote HTTP requests?
-
Is your computer too slow to run Chrome? Just...steam Chrome from the cloud!
Once you have done that, run this: https://github.com/richardanaya/wasm-service, for better offline experience
- GitHub - richardanaya/wasm-service: HTMX, WebAssembly, Rust, ServiceWorkers
- Wasm-service: Htmx, WebAssembly, Rust, ServiceWorker proof of concept
- Htmx, WebAssembly, Rust, ServiceWorker Proof of Concept
What are some alternatives?
django-unicorn - The magical reactive component framework for Django ✨
htmx - </> htmx - high power tools for HTML
htmx-playground - A simple code sandbox for playing around with HTMX. No setup needed!
django-tailwind-alpine-htmx - Simple Task app using Django, Tailwind CSS, Alpine.js and HTMX
yew-beyond-hello-world - yew rust tutorial
reactor - Phoenix LiveView but for Django
axum-browser
django-tailwind - Django + Tailwind CSS = 💚
submillisecond - A lunatic web framework
clerk - Website used by new Anika clients to enter the facts of their case (backend)
grav-theme-wheat - Wheat for Grav CMS