What HTMX does should've been a W3C standard a decade ago, and I've my fingers crossed that some day I'll be able to do what I've done with jQuery and remove it.
Thank you for pushing the state of the art forward in a meaningful (and RESTful!) way.
One bit I've found slightly unintuitive is the swap and settled states. Took my a while to animate in a sidebar how I wanted. It was my fault for not groking it faster but perhaps some more examples or guides in that regard could be useful.
and here is a perfect place for you to contribute to the project! :)
not sure I do now, come to think of it
As someone who is very interested in the space, are there other hypermedia implementation (if is the right word) that you found interesting? Or do you have some pointer for those who want to explore this space?
Personally I really want some kind of hypermedia framework for terminal application, since I often need to work with hardware (or bandwidth) where the only interface is a terminal, and I never feel productive with manually writing the application code, having to reimplement a new client every time.
Also thank you for htmx, I started using for a couple of project, and it really is refreshing. Especially kudos for the various example, that really helped making it "click".
maybe gopher as a prototype example?
adam stepinski (creator of hyperview) is one of the heroes of hypermedia in that he didn't just develop a hypermedia format but also developed a hypermedia client, and you need both for a proper hypermedia system
so, I would say... maybe you are lookin' at the person in the mirror who is going to make that terminal app hypermedia?
Sorry for the newb and lazy questions.
Is there any material on successfully combining htmx with web components? It doesn't look to me like the original design takes this possibility into consideration...
(note: at a surface glance it doesn't look to me like components are in conflict with hypermedia - one could treat them as a side channel that "enhances" the standard set of elements)
My components look like this. The JS and CSS is included in the application's bundles. Ruby renders HTML on the server side.
app/components/breadcrumbs
- _breadcrumbs.scss
- breadcrumbs_component.rb
...
app/components/search_field
- _search_field.scss
- search_field_component.rb
- search_field.js
- selections.html.hamlIt's not really Web Components as specified, but iirc those are generally pretty much JS-dependent? But hypermedia's reliance on server side rendering means that you can just move this logic to the server.
When I started using them, one of the hardest parts was to actually have it imported and built with webpack, since the site focuses on cdn and webpack example is really brief. Same goes for hyperscript
Do you see cdn as a preferred way of usage?
there's a big distortion field around expectations vs reality with webpack.
https://htmx.org/events/#htmx:configRequest
you could jam the outerHTML of the detail.target into the detail.parameters map, maybe based on the presence of an attribute...
If I get around of experimenting with that, and it fits my flow, would that be something you'd accept back into the project as a contribution to the code?
htmx.on("htmx:configRequest", function(evt) {
evt.detail.parameters['my-html'] = evt.target.outerHTML; // or whatever
}
you can jump on the discord and we can help you out when the time comes:Might sound not that convenient for basic things like login forms, but I have frontend code that builds dynamic form fields, which I'd like to not replicate via the backend templating language, if extracting data from HTML itself is a breeze in my case.
Of course I'm going to do that myself anyway, but I'd rather use an established library which also handles in browser page restoration/caching (possibly also fragments), instead of rolling my own JS lib.
he's me
I stopped scrolling as soon as I noticed I have to ask myself what am I posting to this URL?
Maybe digging deeper I could find the reference docs explaining in very vague terms where the payload is coming from. But this was supposed to be simple.
Simple doesn't mean "I should be able to intuitively understand this with under a minute of reading"...
the link here is to the docs, which is more involved
You seemed unwilling to put more than 2 minutes into looking at an example, or 10 seconds into checking what page you were on, yet felt that your experience warranted these dismissive comments which cumulatively proportionally surely took up just as much time.
You aren’t acting in good faith. This doesn’t add to the conversation at all.