https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    I think dropzone fires events that you can listen for on the form
  • m
    i may have added them 🙂
  • m
  • m
    gettin' old's a b, folks
  • m
    so, one idea is to add an hx-trigger to your form to listen for the upload completion event (no idea what it's called)
  • m
    looks like maybe the 
    completemultiple
    event? https://github.com/dropzone/dropzone/blob/main/src/options.js#L778
  • m
    or maybe 
    successmultiple
  • m
    ?
  • l
    I think It might 
    successMultiple
    . I'll check. What would adding the 
    hx-trigger
    do though? Clicking the submit button sends the Dropzone XML request, and the HTMX posts right after.
  • l
    Ehh whatever, I'm so over this. I don't know JS nearly well enough. I'll just make something up on the backend. lmao Thanks anyways @mysterious-toddler-20573
  • m
    🙂 well, I think what you want is for the images to upload then submit the form, but I'm not sure
  • m
    sorry, wish I could be of more help
  • l
    How does the 
    hx-trigger
    dropzone:
    work? My dropzone is declared imperatively in my external JS file. (split by webpack, and seperate from HTMX). Do I have to add my Dropzone to the window? or document? Using just 
    dropzone:
    does nothing for me.
  • e
    Is it possible to fire an htmx trigger to load a select when a form is made visible?
  • e
    And even better load a pair of selects when a form is made visible, in my case, both selects have the same content, if that helps.
  • e
    Discord's search is god-awful BTW.
  • e
    My query, of course, presumes such a trigger exists, though it is entirely possible it does not, given it's a CSS change rather than anything in the DOM as such. Which might just answer my question.
  • e
    Actually I think intersection should do the job...
  • s
    Anyone looked at the Qwik framework? Why is the craze about it?
  • g
    when you do ssr, the server serializes internal state and puts it in the html so the client won't compute the same thing again
  • g
    also it can download event handler code when the event actually happens
  • s
    Okay, so another complication
  • s
    Maybe there are some ideas to learn from them? To incorporate into htmx
  • r
    There was a discussion about implementing lazy attribute evaluation, inspired by qwik
  • o
    It's nice because it allows you to use heavyweight libraries for example without having to think about the resulting bundle size because the initial load will always be tiny and as page features are exposed you download more JS incrementally
  • o
    they call this "finally an O(1) framework instead of O(n)"
  • o
    the guys behind it are crazy about web performance, just look at Miško's twitter threads
  • s
    That’s cool. But it’s essentially layering more complexity on top of complexity. I don’t like that
  • o
    And that's fair, and I agree with you.
  • o
    It's definitely better than other SPA frameworks out there, even including things like Svelte and SolidJS, and I guess that's their target audience.
1...105110521053...1146Latest