https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • b
    I want to create somewhat of a live list
  • m
    that also infinite scrolls
  • m
    so the existing elements should update
  • m
    but scrolling should work too
  • m
    interesting, I will need to think
  • m
    it seems like you could have each page refresh pretty easily, if you can switch from a table to divs
  • g
    maybe: have each "page" (batch of infinite-scrolling rows) be a separate tbody, and reload them individually
  • m
    but that's not ideal obviously
  • m
    yes, that's my thought too
  • m
    You could also sync the infinite scroll and the poll on the element
  • m
    so that they don't interfere w/ one another
  • m
    but you'll need to pass up the total pages on the poll
  • g
    a live, infinite scrolling list seems hard
  • b
    damn
  • b
    I thought I almost had it 😦
  • g
    the further the user scrolls the more the bandwidth use increases
  • b
    mhm yeah I know ... infinite scrolling is not the best of options in general
  • g
    but it'd be a real cool demo if you pulled it off
  • g
    infinite dbmonster
  • b
    hm .... maybe I have to bury that idea 😦
  • m
    no, I think it's doable
  • m
    I think you'd need to keep some state in terms of what pages are being shown, maybe via a hidden input
  • m
    if you have the hidden input multiple times, you'd need to consider the max of all values
  • m
    and then use hx-sync to coordinate the two requests
  • m
    It's doable, I'm pretty sure
  • m
    definitely advanced htmx though
  • b
    mhm ... not the answer i hoped for tbh 😦
  • b
    Is HTMX a good fit for third-party components? Like we use SyncFusion in one of our apps, with Gantt charts and so on. Or is this where I’d want separate server-side APIs, like an “HTMX API” (returning HTML) and a “data API” (returning JSON)?
  • m
    how does Hotwired: Turbo compare to HTMX?
  • m
    Why use HTMX over turbo?
1...859860861...1146Latest