got it. thanks

htmx + alpinejs + bootstrap on the front, cgi+html on the backend then for the embedded project

I just wanted to say thanks for all the hard work on HTMX/Hyperscript. Coming from primarily a machine learning/data background it makes doing web stuff a lot more fun. Plus it brings me back to making hypercard games when i was a kid.

Hey i have a question, how do you guys toggle input fields based on a earlier select/radio field

do you use htmx of it

Hi do you have an exemple of what it would looks like ?

one two

sure i can do this via jquery

In case it wasn't obvious , @User response uses hyperscript

html
<select id="field1">
  <option> one </option>
  <option> two </option>
</select>

<input _="on change from #field1
  show when #field1's value is 'two'">

(in my earlier days here the context switch to hyperscript used to throw me into a what-the-*-is-that loop)

Angular dropped IE11 support in v13, released last month. Just sayin' https://blog.angular.io/angular-v13-is-now-available-cce66f7bc296

Nice. On the dev page, the link to the intro post isn't a link. Apart from that, though, looks fine!

any php people who want to chime in: https://github.com/bigskysoftware/htmx/discussions/706

Fixed and published https://thisweek.htmx.org/issue/7/

I have a situation where the following is happening: 1) we're using hyperscript to generate a custom event - with a parameter - when the user selects something on the page 2) that event then triggers several elements on the page to update themselves - via htmx. The problem is that in order to update themselves, our page elements need to include the parameter passed with the event - i.e., we need to add that incoming parameter to the

hx-vals

attribute of each element. How do I 'catch' the parameter inside the

hx-trigger

, so I can include it in the

hx-vals

?...or is there a better way to do this?

@User what I've done for situations similar to the one you described is that I create listener for the custom event that then sets a global variable which is then accessed from hx-vals as follows

hx-vals='js:{param: global.variable}'

To be honest it feels kinda hackish but it works. I've often thought that there might be a way to make it less hackish using hyperscript but I haven tried it yet

Thanks for the suggestion, @colossal-glass-79762 - we’re doing something similar, just storing the value inside an element’s attribute instead of a global. It’s a workaround, for sure.

@User storing the value as as the elements attribute is even better than my workaround.

I have a blog post form that must allow user to pick multiple authors from a very long list. How would you solve this with HTMX? In the past I have used something like Select2 or Tom Select.

would still use select2 or similar

feels like he's right and the SPA infatuation is waning a bit

I agree.

I really hope web components ecosystem grows and becomes the default answer to when you need a stateful UI component. They should play nicely with HTMX.

The conclusion to my series is now available! https://blog.bitbadger.solutions/2021/a-tour-of-myprayerjournal-v3/conclusion.html

BTW - I can't remember who said they weren't sure about writing about their code publicly. But, whoever you are, in this post I actually talk poorly about my own code. 🙂

They can't talk bad about you if you beat them to it! LOL

Some talk about htmx in the comments on the Lobste.rs post on Hotwire: https://lobste.rs/s/lifxol/time_is_right_for_hotwire