https://htmx.org logo
Powered by
# htmx-general
  • m
    cool feature
  • g
  • m
    i had always wanted to take some time to learn erlang, maybe I'll learn elixer instead at some point
  • g
    you don't want to learn erlang
  • g
    erlang is terrible for developers. amazing vm, terrible language
  • i
    Agree. I tried it years back and just couldn’t get into it. Now Elixir is my favourite language and Phoenix is my favourite web framework.
  • i
    I hope I’m not coming across as argumentative for the sake of it but they couldn’t be more different. Websockets are stateful and no matter how efficient LiveView is it is harder to scale than stateless http with htmx. I actually found htmx because of the issues I was having with websockets/LiveView. The demos all look simple and amazing but simple state management between pages and disconnects were having having my life.
  • g
    well we have pretty different experiences
  • i
    Yeah I wish I had your experience. I think I’ll probably create a demo of both ways and try and show the benefits of http and htmx over websockets and liveview instead of very badly explaining the benefits.
  • g
    i created a pretty complex fulfillment service in liveview. order creation, batching, address validation, shipping label provisioning, asset management, stock keeping. it was not really ever a problem.
  • e
    Is it possible to manipulate dom value before submitting to backend? This is what I have:
    Copy code
    <script>
  htmx.on("htmx:beforeSend", function(evt) {
  document.getElementById("pub").value = "new value"
  console.log(document.getElementById("pub").value)
  }
</script>
    It prints the new value in console; but the backend still gets the old value. Is it possible to set new values before sending request to the backend?
  • i
    The reason why the updated dom value isn't being submitted is because once the event has been triggered it contains everything it needs to perform the request. The solution is to modify the event data not the dom...
  • i
    window.addEventListener("htmx:beforeSend", function (evt) { console.log(evt) evt.detail.requestConfig.parameters["pub"] = "new value" });
  • s
    A small Calendar component built with htmx Demo: https://htmx-calendar.herokuapp.com Code: https://github.com/rajasegar/htmx
  • m
    looks great! Are you having fun?
  • s
    Absolutely
  • m
    some pretty slick code!
  • m
    that's all that matters 👍
  • s
    Tabular data demo with sorting, searching and pagination with Node and htmx Demo: https://htmx-tabular.herokuapp.com/ Code: https://github.com/rajasegar/htmx-tabular
  • g
    Any chance of releasing 1.3.2 soon?
  • u
    Can it be searchable by ★★★★ (stars) or by dollar signs?
  • u
    Great usage examples btw!
  • m
  • m
    release tomorrow
  • g
    If I add a htmx.on('.my-container', 'htmx:AfterProcessNode' ...
  • g
    and then replace the inner html of .my-container outside of htmx and run htmx.proccess on it. The first time the afterProcessNode triggers my code. But the next time it doesn't
  • g
    At first I thought that it had something to do with replacing the html... But if add an htmx.process on the element that is triggered when clicking the afterProcessNode is only triggered once
  • g
    Aha... It only triggers the event once
  • g
    Nvm. I just triggered my own event instead 🙂
  • s
    No , the search is based only on the name field
1...200201202...1146Latest