https://htmx.org logo
Powered by
# htmx-general
  • b
    Agreed, really great work by @User!! Looks like the htmx navigation bar links to redirects which I've resolved by adding trailing slashes (https://github.com/bigskysoftware/htmx/commit/b21e40e12a666f833e7e6c3d2db3e21f81890cbc).
  • q
    Hey guys and girls 🙂 Is there any open-source example of some moderately complex app written using htmx? just for reference
  • b
    There are lots of examples to pick and match from at https://htmx.org/examples/. Not sure what exactly you mean by "complex" in this context though.
  • b
    Congrats 🎉 I updated the version number in the docs, as well as added SRI instructions, which needs to be pushed to the live site: https://github.com/bigskysoftware/htmx/commit/2499401500bff691fe5b4fb02ccf6c618c7ed3c5
  • q
    It'd be great to have an example of the complete web app, with auth, role model, admin interface, some small but real business logic.
  • b
    It's called open source for a reason 😉
  • b
    Plus most of what you list requires a back-end, so not sure how useful it would be to build an opinionated front-end demo.
  • m
    I can see lowering it down, but 0 seems aggressive. For your use case I don't know why the settle step would make things feel slow, I'd like to understand that...
  • m
    Thanks ben!
  • m
    I would like something like that, but the problem is that since htmx is back-end agnostic, we'd probably have to do a bunch of them, and I haven't had the time to do so. The good news is that, by and large, an htmx-powered app will look like a normal app on a given server side platform. But at some point I would like to start work on, for example, the TODO app on various platforms.
  • m
    One thing to note: the website is deployed directly from master, so if you push up a fix it should go live in about a minute or so (netlify auto-deploy)
  • b
    Ah, good to know!
  • a
    Question on the difference between 
    Intercooler.ready
    and 
    htmx.onLoad
    ... in the Intercooler case the element being passed in is the root element whose content is being swapped (e.g. 
    body
    ). With htmx the element is the content being swapped itself, correct (if using the default innerHTML swapping strategy)? If so, what would the best approach be to replicate the "get root element being swapped" with htmx?
  • m
    o_O
  • a
    I don't know if I should feel proud or ashamed of that reaction 😅
  • a
    Ok, given something like this:
  • a
    Copy code
    <body>
  <div id="nav" hx-boost="true" hx-target="#main">
    <ul>
      <li><a href="/path"></li>
    </ul>
  </div
    
  <div id="main"></div>
</body>
<script>
    Intercooler.ready(function(rootContent) {
        init(rootContent);
    });                               
<script>
  • a
    You then click on 
    <li><a href="/path"></li>
  • m
    yes
  • a
    The 
    rootContent
    element passed to the 
    Intercooler.ready
    callback, would be 
    <div id="main">
    , right?
  • a
    With htmx, if you replace the 
    Intercooler.ready
    handler with:
  • a
    Copy code
    htmx.onLoad(function(elt)) {
      init(elt);
    }
  • m
    yes
  • m
    these are intended to be equivalent-ish
  • a
    ... then 
    elt
    will not be 
    <div id="main">
    , right?
  • m
    lemme look
  • m
    if it isn't elt, it might be the new content
  • m
    that is being put within elt
  • a
    It's the new content, yes
  • a
    So my question is - I want 
    <div id="main">
    in the htmx case, so I can initialise event handlers and stuff on it. Possible?
1...122123124...1146Latest