https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • t
    I might give it a shot next week when I'm on vacations
  • m
    In the background I have been thinking about how to implement a merge swap strategy in htmx based on this: https://github.com/choojs/nanomorph/blob/master/index.js
  • m
    The algorithm of this (and of morphdom, from which it is derived) actually isn't as bad as it seems at first
  • m
    There is one improvement that I'd like to make: before doing the merge, find all the elements with ids in the old content and new content and "merge them up" into temporary hash tables on their parent elements. This could be pretty fast, and then you could make slightly more informed decisions about when to merge based on the structure of children, without needing to inspect them at each node.
  • m
    I think that, coupled with the new shared element transition API (optionally, if it is supported) would make for a heck of a user experience
  • m
    I enabled 
    hx-boost="true"
    on the of my bootstrap 5 site. A strange side effect I've noticed is that BS modal backgrounds get progressively darker the more links I click, until finally they are black. Any ideas what's going on here?
  • m
    I would guess that they are getting overlayed on top of one another
  • m
    for some reason they are being preserved between navigations
  • m
    ah sorted it, i moved the BS JS file to the head and the issue went away (it was a the bottom of the body). I remember I had a similar issue with Turbolinks...
  • m
    Forgot you need to move all the JS to head for this to work. Might be worth making a note of it in the docs?
  • l
    You know, if I hadn't seen videos of you, I think I could be easily convinced that you're Roy Fielding using a different screen name... LOL
  • l
    In my day-job, we're moving into a cloud infrastructure, so we have to change all interfaces to run over port 443. I'm having such a hard time holding my tongue when people describe them - "So, is this going to be SOAP, or RESTful JSON?"
  • l
    🤦‍♂️
  • l
    (and, hooray for me, I guess - mine is SOAP!)
  • m
    \> soap \> 2022
  • l
    Running on Java 6 EE!
  • l
    (dang - Discord doesn't have dinosaur emojis...)
  • l
    I'm writing it in Kotlin, so I will have a bit of sanity left when it's done. This is the application for which I've made that proof-of-concept I talked about several months ago; it's a "patch it 'til you can replace it" scenario.
  • q
    With net beans and ASN.1?
  • l
    Spring 2 (I think)
  • l
    It runs on a version of JBoss that makes the network security folks nervous... LOL
  • q
    And by nervous you probably mean "reaching for the extra bottle of Jack"
  • l
    Ahh - it's a semi-closed network, and they've got the thing firewalled properly. It wasn't vulnerable to the Log4J problems because that only affects version 2, and it uses v1.
  • m
    \> security by being so impossibly out of date that no one even bothers with an exploit
  • m
    I love it
  • l
    I don't want to rip on it too hard; its existence (and dependence on Flash leading up the drop-dead date in 2020) is why I have this job. I'm glad I've been able to work on other things, but it's still more or less mine (along with one other developer) to keep going until we can get a replacement fielded.
  • m
    yeomans work
  • l
    I have to say, though, I'm probably writing more XML for this web service than I've written since I worked on the application that embedded SQL queries in XML files.
  • l
    XML is like violence - if you think it's not the solution, you're clearly not using enough of it.
  • q
    So when you say you've got a problem and you'll use XML to solve it... now you have two problems.
1...794795796...1146Latest