From 62472709d08f43c95286b6d3af6046420bcd92e6 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Sat, 28 Jun 2025 08:49:52 +0100 Subject: [PATCH] HTMX update - online edit of handbook/troggle/trogspeculate.html - on dev machine 'SnowWhite' --- handbook/troggle/trogspeculate.html | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/handbook/troggle/trogspeculate.html b/handbook/troggle/trogspeculate.html index c06c42b79..a10696a95 100644 --- a/handbook/troggle/trogspeculate.html +++ b/handbook/troggle/trogspeculate.html @@ -83,7 +83,13 @@ the stability we want that Javascript is failing to provide, such as NiceGUI and Pynecone. Though things running on wasm are perhaps going to be more future-proof. [2023].

It looks possible that the <HTMX> approach may settle down to replace HTML5 and also subsume a lot of what is now provided inside Javascript frameworks. We will wait until then. -

[Update April 2023] It does indeed look as if HTMX is likely to be important in the future when we want to refresh only parts of pages. See this article: A 'No JS' Solution for Dynamic Search in Django. Something along these lines seems likely to appear in a future release of HTML. +

[Update April 2023] It does indeed look as if HTMX is likely to be important in the future when we want to refresh only parts of pages. See this article: A 'No JS' Solution for Dynamic Search in Django. + +

[Update June 2025] Yes, HTMX is catching on:

Our biggest problem

We need: