https://htmx.org logo
Powered by
# htmx-general
  • f
    Interesting, like a popup banner across the top saying the item has changed. I think I've seen that recently on Freshdesk's interface. Once the system has realized there's something out of date it can stop polling.
  • t
    If you want to do everything in one request, use 
    hx-swap-oob
    to swap out the data. With careful positioning of your input fields, this wouldn't necessarily affect them. For example, I have a table with a select input on the table header which swaps just the table body, leaving the input intact.
  • f
    Yeah the interface is terrible so the data portion of the lists are all separate tables that can be swapped out (with the input being jut below the table), I just thought that 100 table oob swaps might be a bit too unwieldy for htmx. And it needs some ugly backend code for the templates but that might be the best way
  • t
    You have 100 tables?
  • t
    Anyway, put the input field in your `tfooter`s and replace only the 
    tbody
    elements for minimal impact on user experience.
  • t
    I happen to be working on a thing that is showing 3 tables, 2 of which have pagination while the third can be filtered to show different data. I resolved this with just some 
    hx-select
    attributes so the page still works fully without javascript enabled. The server currently still renders the whole page regardless of what I'm selecting, but I'll be implementing some changes for that eventually™️ so it only renders what it has to
  • f
    Give or take, there are anywhere from 1-20 groups of lists showing for a user and each group has 8 lists.
  • t
    That's a lotta tables
  • t
    I will say this though, if the browser can load them quickly enough for you on initial load, htmx oob-swapping all of them shouldn't necessarily be noticeably slower.
  • f
    It's a little dumb. But it's a maintenance system that shows, for example, a car, with a bunch of related/independent lists and the user could be showing one or all... the browser load time is fine
  • t
    As long as you're not polling every half second or whatever
  • f
    Sometimes the lists gets a little lengthy for good user flow, but the users like it that way
  • f
    haha no, I was thinking once per minute or so
  • t
    Honestly I'd just make them each do a separate poll
  • f
    The thing that prompts it is often users trying to delete the same list item, so one person deletes it but then the next gets the 404.
  • t
    100 requests per minute isn't a big deal
  • f
    Yeah? and the multiple of that wouldn't create too much request noise?
  • f
    Oh each table even?
  • t
    m8 you wanna see request noise try opening your network tab on something like gmail
  • f
    100 requests per minute x 30 users... we're still pretty low I suppose 🙂
  • t
    You can make it so each request only really fetches the data it needs, so it's 100 mini-requests, not 100 requests for the full page.
  • f
    Fair
  • t
    Now, what I don't know if/how you can do is have a delay on each table so they don't all trigger at the exact same time
  • f
    ahh like a slight offset for each That might be more difficult since eventually the second based timers would land at the same time
  • t
    Something like 
    hx-trigger="every 60s + (table_count/60)"
  • t
    Which obviously wouldn't work but should be a good example of what I mean
  • f
    Yeah, no that makes sense
  • t
    I guess 
    load delay:60s
    so each one is retrieved every minute, but due to natural request delays, they would run out of phase after the first minute
  • m
    Could also check proximity to the user’s viewport or cursor and prevent the request for anything unlikely to benefit from polling?
  • f
    Well, I'm going to give something like that a go and see what happens. It is the most straight forward way, previous when I considered it I thought maybe it was too simplistic and would create too much network traffic.
1...669670671...1146Latest