https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    still need to think more
  • m
    maybe the right thing is to introduce a 
    queue
    modifier to the trigger, and then default it depending on the element type: buttons and links don't queue, other things do.
  • m
    the 
    disable
    and 
    caret
    problems are tough. Still thinking...
  • g
    So, you're already well ahead of me in thinking about this.
  • g
    I'll add that many websites will style things like 
    a
    and 
    span
    to look like buttons. So, making those rules based on element type might be a problem for them. (That's not necessarily a bad thing.. just forcing them to be more symantic)
  • m
    they can always access the setting by being explicit
  • m
    this also reminds me of a feature I want to add to hyperscript where you can say:
    Copy code
    js
  while some expression <some reversable operation>
  • m
    e.g.
  • m
    Copy code
    js
  while .htmx-request add .foo to me
  • m
    And use observers to make that all work
  • m
    OK, family time... think more kids
  • a
    I had a stab at extending the path-deps extension. I logged a ticket (https://github.com/bigskysoftware/htmx/issues/286) and created a pull request (https://github.com/bigskysoftware/htmx/pull/287). Could you please have a look when you have time and comment on it? If you think its ok I'll add the tests and documentation
  • r
    Is there a tl;dr of how to dynamically populate an element with json websocket data?
  • m
    not that I'm aware
  • m
    Thank you, I will try to look at this tomorrow!
  • r
    Ah I'll hold off on htmx a bit then
  • m
    @User yes, I think that's probably the smart play. The websocket stuff is relatively new.
  • m
    If you are willing to work with it a bit, you could probably contribute there
  • m
    but that is a commitment
  • m
    yeah, ok, looking at the web socket code, we do give you a crack at transforming the JSON before it is processed:
  • m
  • m
    So you could write an extension to transform the JSON into HTML on the client side
  • m
    however, if the data is coming down in JSON, the advantages of running it through htmx seem attenuated
  • m
    I guess there is the nicety that you can target elements by ID w/ the stream, and you get the OOB swapping behavior, so that might be useful
  • a
    Another Intercooler -> htmx question: is there a htmx equivalent for 
    ic-trigger-from
    ?
  • m
    the solution here would be hyperscript, and triggering an event on the intended target:
    Copy code
    html
  <div _"on click trigger makeRequest on #otherDiv>...</div>

  <div id="otherDiv" hx-trigger="makeRequest" hx-get="/whatever">...</div>
  • m
    would you mind starting to collect all these things into a markdown file so we can publish an intercooler -> htmx porting guide?
  • a
    😂 that’s exactly what I was thinking
  • a
    Sure. I’m going to be porting an existing app from intercooler to htmx and was going to be documenting my findings anyway. I would be thrilled if it could help other folks as well 😊
  • m
    alternatives you could use the javascript api:
1...112113114...1146Latest