https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    I want to keep them separate
  • m
    a tokenizer and parser gets pretty big
  • g
    Why wouldn't it? Wouldn't this work?
    Copy code
    on whatever alert("Dude, stop") then wait 200ms then js {tellMom()}
  • m
    yes, but if that js did something async (e.g. 
    setTimeout()
    ) it wouldn't be transparent
  • m
    the way that 
    wait
    is
  • g
    I see. That makes sense.
  • g
    On HTMX + Hyperscript, yes. I's easy to see them as separate libraries. It probably makes more sense like that. Maybe I'll just push for tightening the bonds between them, so that certain features of each are exposed to the other. My best example right now is the swapping logic. I'd really like to try using that throughout Hyperscript.
  • m
    yeah, the right thing there is introducing the right cut points from an events standpoint so that extensions can be implemented entirely in terms of events, at which point hyperscript is as good as anything else
  • g
    Yes. I think I follow you.
  • g
    And, let me know if you'd like another pair of eyes (or hands) on Hyperscript. I'll probably need you to lay the groundwork, but I'm happy to help fill in spaces once they're ready.
  • m
    👍
  • m
    prob mid-late december
  • g
    For sure. Everyone's swamped with regular life this time of year -- not to mention the COVID, too.
  • f
    I'm definitely excited about hyperscript.
  • f
    Embedding little bits of arbitrary functionality as attributes on a tag fits really well with what I'm doing.
  • f
    The SSE queries work BTW. I can now have a single hx-sse'connect:...' and multiple 'swaps'.
  • g
    @User nice!
  • f
    Copy code
    with doc:
    with tag.div(data_hx_sse = 'connect:/sub/{query}'.format(
                                            query = '-'.join(list_id))):
        for id_component in list_id:
            tag.div(data_hx_trigger = 'load',
                    data_hx_get = '/req/{id}'.format(id = id_component),
                    data_hx_sse = 'swap:{id}'.format(id = id_component))
  • f
    I'm probably doing something wrong still ... but good enough for progress.
  • f
    Now I just got to work out the tailwind CSS magic to lay out the components as I want.
  • m
  • m
  • m
    htmx 1.0 is up on HN
  • m
    this is one of the funniest tweets I've ever read: https://twitter.com/hncynic/status/1332475208570183682
  • g
    It's more likely than you think.
  • l
    A comment I made: "HTMX encodes server interaction in hypertext rather than in Javascript. For those with intensive back-end logic and only light interface needs, HTMX offers a incremental way to add front-end interactivity without having to take the deep dive into Javascript frameworks. Longer term, the concept of encoding server interaction in hypertext seems rather novel to me. Perhaps this approach may be one of many missing pieces towards an ecosystem of interoperable hypertext-based web components."
  • m
    just so @User
  • l
    To the HN commenter concerned about 
    hx-
    prefix, I refer to RFC 6648, which deprecates 
    X-
    for HTTP headers.
  • m
    🙂
  • m
    Don't spend too much time in the HN comments section. I've already wasted way too much time there today.
1...808182...1146Latest