There's a lot of explaining concepts and not a whole lot of just showing you how to fucking use the thing

That's why I tried staying on backend and desktop as much as possible 😄

Sounds like it could be usefull to have a way of preventing addons from messing with the page when you're doing development. Or just not have addons

SOLVED: Hi All, just starting with htmx after many years using IntercoolerJS.... Just trying to get debug extension to work. I have included htmx using

Do I need to include the debug extension separately? If so, how?

I have added

hx-ext="debug"

to my element but see nothing in the console

ANSWER:

<script src="https://unpkg.com/htmx.org/dist/ext/debug.js"></script>

you/they lost me at ``npm init``

They work pretty well if you work on a network where things from the big, bad, dirty Internet are not to be trusted (especially from such sketchy places as Maven, NuGet, and npm), but we can have whatever we want in our source repos. (And even better when our configuration management deems them "build dependencies", so we don't have to track them / have a ticket to change them / etc.) Uh, I mean, in theory, I guess...

happy to announce htmx 1.7.0! https://twitter.com/htmx_org/status/1496123303290888192

the website is definitely very concept heavy, but after looking around a bit I found this:

html
<div ::app-state="./AppState" 
     app-state:1234="{count: 321}">
  <div decl:template="./Counter_template"
       on:q-render="./Counter_template"
       ::.="{countStep: 5}"
       bind:app-state="state:1234">
    <button on:click="./MyComponent_increment">+5</button>
    321.
    <button on:click="./MyComponent_decrrement">-5</button>
  </div>
</div>

so it looks somewhat akin to AlpineJS. Rich Harris mentioned it in his "Have SPAs Ruined The Web" talk as something that "aggressively lazily loads" things. At first glance I would pick hyperscript or AlpineJS for this sort of thing, but it's always good to have more competition to foster ideas!

Honestly didn't feel much like hyperscript at all to me, except for the locality aspect. Their big deal is that everything (really, all state) is serialized to the DOM. There's no state kept in global variables or closures or promises. So the idea is that your framework on the backend sends state in this format, and thus they have a single very small loader that's just a bunch of document queries to find elements affected by a state change, then invoke the lazily loaded js functions to "deal with it" sort of like a react/redux reducer. In some ways it's almost the opposite of hyperscript, because the #1 priority focus is on reducing time to interaction at the expense of being harder for the developer.

This screenshot is wild. I knew hx-sync was coming, but had no idea it would be usable like this. Well done @User!

I get an error for the bottom link

looks like the quote got stuck into it

I've been building a thing for work using the https://arc.codes framework, and noticed that they have started to advise that lambdas/functions should return HTML rather than JSON. there was this interesting line in https://fwa.dev/before-and-after that seems HOWLy: "A different way to solve all this complexity is to move up the cloud vendor stack. A Functional Web App (FWA) is authored completely as single-responsibility cloud functions that can render HTML-first dynamically, incorporating the full-stack such as a managed database."

that's awesome

HOWL on lambda

hyper text on whatever lambda

Ooh this stern new version of htmx is telling me off about stoopid things I've done and I'm loving it (better than McD's)

HOWL + FWA = HALF WOW

the.missing.style will supply the remaining wow.

eep: also = HOW FLAW. we'll just ignore that as unparseable.

🙂

Apparently, these things exist... https://www.amazon.com/Keyboard-Computer-Customized-Shortcut-Combination/dp/B09B3K5HN1

okay so...general not htmx question: is there anything on xhtml nowadays, yes it kinda was abandoned, but what if i want my pages with custom nodes and props?

Web-components seeks to solve that to some degree, but of course uses JS instead of XML extension: https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements

their standards are shit

i don't like them

Question: does

hx-disinherit

work with

hx-indicator

?