Django-LiveView/docs
1
0
Fork 0
mirror of https://github.com/Django-LiveView/docs.git synced 2025-12-31 05:32:23 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Use one.el fork with table support

Browse Source 
- Simplified onerc.el by removing table workaround
- Updated build.el to load fork from local path
- Added one.el fork as submodule with table support
This commit is contained in:
Andros Fenollosa
2025-12-27 10:32:21 +01:00
parent 8d62de1f62
commit 9ad0814822
4 changed files with 23 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.gitmodules vendored Normal file
View File

@@ -0,0 +1,4 @@
[submodule "one.el"]
path = one.el
url = git@github.com:tanrax/one.el.git
branch = add-table-support

7
build.el
View File

@@ -4,6 +4,11 @@
'("melpa" . "https://melpa.org/packages/") t) '("melpa" . "https://melpa.org/packages/") t)
(package-initialize) (package-initialize)
(package-refresh-contents) (package-refresh-contents)
(package-install 'one) ;; Install one.el dependencies
(package-install 'jack)
(package-install 'htmlize)
;; Add fork to load-path and load it
(add-to-list 'load-path "/usr/src/app/one.el")
(require 'one)
(find-file "/usr/src/app/one.org") (find-file "/usr/src/app/one.org")
(one-build)) (one-build))

1
one.el Submodule

Submodule one.el added at 19605b02b2

20
one.org
View File

@@ -95,19 +95,23 @@ That's it! No page reload, no API endpoints, no REST, no GraphQL, no frontend fr
#+ATTR_HTML: :class center-block image image--benchmark #+ATTR_HTML: :class center-block image image--benchmark
[[#/img/benchmark-response-time.webp][Response Time Comparison]] [[#/img/benchmark-response-time.webp][Response Time Comparison]]
- **LiveView** (WebSockets): **9.35ms**, 450 bytes - Real-time dashboards, collaborative apps | Framework | Technology | Response Time | Data Transfer | Use Case |
- HTMX (AJAX): 16.48ms, ~37 KB - Modern UX with minimal JavaScript |--------------+-----------------+---------------+---------------+--------------------------------------|
- Unicorn (AJAX): 26.76ms, ~71 KB - Complex forms with reactive state | **LiveView** | WebSockets | **9.35ms** | 450 bytes | Real-time dashboards, collaborative apps |
- SSR (POST + redirect): 47.25ms, ~8.5 KB - SEO-critical pages, traditional CRUD | HTMX | AJAX | 16.48ms | ~37 KB | Modern UX with minimal JavaScript |
| Unicorn | AJAX | 26.76ms | ~71 KB | Complex forms with reactive state |
| SSR | POST + redirect | 47.25ms | ~8.5 KB | SEO-critical pages, traditional CRUD |
Django LiveView is approximately **43% faster than HTMX** and **80% faster than traditional SSR** through persistent WebSocket connectivity. Django LiveView is approximately **43% faster than HTMX** and **80% faster than traditional SSR** through persistent WebSocket connectivity.
*** Technology Comparison *** Technology Comparison
- **Transport**: LiveView (WebSocket) | SSR (HTTP) | HTMX (AJAX) | Unicorn (AJAX) | Feature | LiveView | SSR | HTMX | Unicorn |
- **Update Type**: LiveView (Real-time) | SSR (Full reload) | HTMX (Partial) | Unicorn (Reactive) |--------------------+------------------+-------------+-------------+-------------|
- **Multi-user**: LiveView (✅ Broadcast) | SSR (❌) | HTMX (❌) | Unicorn (❌) | **Transport** | WebSocket | HTTP | AJAX | AJAX |
- **Infrastructure**: LiveView (Redis + Channels) | SSR (Django only) | HTMX (Django only) | Unicorn (Django only) | **Update Type** | Real-time | Full reload | Partial | Reactive |
| **Multi-user** | ✅ Broadcast | ❌ | ❌ | ❌ |
| **Infrastructure** | Redis + Channels | Django only | Django only | Django only |
*** What makes it different? *** What makes it different?