I love Intercooler, but without an active community any framework is worthless over the long run imo

Cannot hurt to get used to the new vision of what Intercooler should have been

😀

Thanks for all your awesome work on that note

Intercooler will be supported indefinitely

Boosted Boards also gave life long warranty before they went bankrupt

And indefinitely is quite a long time heh

lol tricks on all of you: I’m already pre-bankrupted

Well, been looking for that dono-button on GitHub

😀no worries, intercooler will be around for a long time. I use it in multiple apps that keep me fed.

Working on that HTMX-Patreon site, powered by Intercooler I hope

BuyMeACoffee is also ok – just a thought

Good projects should be supportable

Think that's gonna be my workaround for now, in case anyone needs it. Could need some improvement, i.e. allowing for args. It's not very elaborated, but good enough.

javascript
/* ic-action 2ct replica for htmx */
document.addEventListener('htmx:afterSettle', function(evt){
   var fnstring = evt.detail.elt.getAttribute('hx-action');
   var fn = window[fnstring];
   if (typeof fn === "function") fn();
});

Well... I'm close. Boosting the form did make it respect the redirect, once I returned it instead of an

HX-Redirect

header and a 201 with a location header. (This was a "create" action.) However, the headers on the 302 request didn't fire my event listeners (I think XHR may be eating them), so my confirmation message didn't show. All fun things - I suppose I could implement a server-based message queue for those, and return them with the payload on the response redirection... BTW, I ended up changing the "page" logic to include the title tag in the

head

element, then the rest of the page stuff in the

body

tag. That way, I don't replace the scripts and styles from the head, or the toast and scripts from the footer, but the navbar and the content all come in one request. This has the added bonus of navigation now scrolling to the complete top of the page. (I had tried to make that work, but had been unsuccessful up to this point.) At any rate - I'm pleased with the progress, and may play with it a bit while I'm on vacation. It's a disconnected vacation, though, so I'll see you all back in a week or so. 🙂 Thanks again for all the help!

the way I see it, htmx is simple and elegant enough that its viable even if development stopped tomorrow. Simplicity and elegance has advantages like that.

Fwiw we made heavy use of the ic-action family of attributes… but I tell you what, since starting the migration to htmx, the replacement of them with hyperscript event handlers have been great. It’s also helped to do away with some clunky “return false” attributes in place to stop client side Intercooler events bubbling up inappropriately. In my mind the clear separation of mostly dom swap management that htmx does, along with hyperscript (or alpine or similar of course) listening for the htmx lifecycle events and doing client-side things as appropriate, is brilliant.

@miniature-controller-37356 👆

Pleased to hear of your progress 👏

This is a plaque-worthy statement and I couldn’t agree more! 👏👏

Yeah, guess that makes sense. Would you mind posting some advanced examples to get started with htmx and alpine? The hardest part for me is getting past a handful of examples to get the hang of it and adapt them quickly to various use-cases.

We went with hyperscript instead of alpine, so can’t help you there. Here’s the beginnings of a Intercooler to htmx migration reference I created a while back. I’ve actually learnt a lot since then and should probably expand it a bit, but perhaps it might help a little as is: https://htmx.org/migration-guide/

Thanks. Unfortunately the guide is heavily leaned on Hyperscript examples... not that I have anything against Hyperscript, the syntax just seems super confusing to me and I'm worried I won't be able to properly use it. Don't really have any JavaScript background.

if there are any examples you want translated into alpinejs or vanilla js, just post them here, someone will be able to help

has anyone used has anyone used https://turbo.hotwired.dev/, thoughts on hotwire vs htmx?

In the thread: > and I don’t see how an htmx app could ever work with JavaScript disabled Because Turbo would work with JavaScript disabled 😕 ? Does anyone know (or guess) what is the fallback of Turbo frames when there is no JS?

Turbo apps usually send full pages and let the client pick out the right element. This is also possible with htmx.

It's simply left up to the developer to do progressive enhancement

if no js then there is no hx-boosted header - send the full page, otherwise send partial page 🧐 thats what I've been doing