https://htmx.org logo
Powered by
# htmx-general
  • m
    I might have one on the old intercooler website (htmx is intercooler 2.0)
  • f
    With what little you know of my needs, which examplle from https://htmx.org/examples/ would you recommend I look to decompose the most?
  • m
    🤔
  • m
    unfortunately we don't have a good polling example right now
  • f
    Well at least it is not just me for lack of understanding what I was looking at!
  • m
    I remember putting this example together back for intercooler: https://intercoolerjs.org/2016/05/25/twelve-html-attributes-explained.html
  • m
    I should port it to htmx
  • f
    Looking 👀
  • m
    the "Making The Table "Live" section is relevant
  • m
    but it's really simple
  • m
    in htmx you just would do something like this:
  • m
    Copy code
    html
<table hx-get="/the/url/to/render/the/table">
       hx-swap="outerHTML"
       hx-trigger="every 5s">
 ... table contents
</table>
  • m
    I am assuming you would swap the outerHTML in this case, but ymmv
  • f
    OK, I can look at per row replace or full table replace
  • f
    To that end a question on how to actually poll and where to trigger updates from.
  • m
    sorry, have to run, but will try to answer in a bit
  • f
    Knowing that the boto call is expensive, and there is at least one per row of data in the table,
  • f
    yeah, will just spam here, appreciate feedback, when / if
  • f
    I have a sqlalchemy db on the back end, which I effectively render the table from.
  • f
    The boto calls complete, stuff the answer into the db and then render the overall table
  • f
    However, this implies I will need to seperate the background polling against AWS for vm states, and pump that into the db, then seperately have the front end poll into the back end for a rerender of the table with whatever happens to be in the db at the time.
  • f
    However, this strikes me a messy, with unnecassary latency of available data.
  • f
    So something that allowed me to do a set of boto call updates into the db, then trigger an update to the web page from end, and set itself on a delay before running again ( in say 30 seconds )
  • f
    I am just not sure what the advised system behaviour is here, and don't want to jump too deep on an ill advised....
  • f
    Right now what happens is on intial call to render of the page, all boto calls are made, db updated, page rendered, and pushed to the front end with a 30 second forced full page refresh.
  • f
    So I think I should have on entry to the page, render what we know in the imeadaite from the db, push to the front end, trigger a chain of calls to boto AWS, which when complete update the db, rerender the relevent tabel and update that section on the front end, while also triggering the next cycle of boto AWS calls in X seconds.
  • f
    Just not really sure how / where to do any of this 😦
  • g
    If you want to replace a row (or group of rows) try putting the hx- attributes on a tag. Most browsers/js engines barf when you mess with individual rows. This affects all javascript libraries, and htmx is not immune.
  • f
    I think you have me pursuaded to treat this at the top level table replace
  • f
    This way I can seperate the "update the table from db" into its own code, and then worry about how to scheudle the update of the db itself and trigger the table update
1...492493494...1146Latest