https://htmx.org logo
Powered by
# htmx-general
  • m
    one thing that's a little suspicious is the double quoting of the '"GET"'
  • m
    verified that the code is working locally, something is up
  • m
    maybe can you inspect the DOM and see if there is some server-side escaping going on?
  • f
    I have a flask applicaton that I have written based on the mega flask tutorial as my starting point, and now everything is working fine, I have the vast majoriity of my intenteded functionality, and its skinned through bootstrap, so seeing as I have never been a web domain programmer ( lots of embedded and up experience ) I am quite happy.
  • f
    However, its time to move the overall lifecycle from being a full page refresh every 30 seconds with long calls to AWS APIs to check VM states ( and similar ) to something a little more refined.
  • f
    I am pretyt sure that HTMX is the way forward, but despite going throguh the Talk Python to me trianing course, I still don't have enough of a skeleton to be confident on where to start.
  • f
    Basically I have a table with a row for each virtual machine, with infomration such as AWS instance ID, IP addresses etc.
  • f
    Also a single entry on that row for AWS machine state ( Stopped, Starting, Running, Shutting down, etc )
  • f
    To get that status it is a relatively long running call to an AWS boto API, so a full page refresh is way too clunky, with multiple rows in the table taking a while.
  • f
    I imagine I should have a table data element that is polling to trigger a API call and updating on response, or being kicked by a polling driven from the python flask server side.
  • f
    I am struggling to get to a releavant example of similar behaviour.
  • f
    I am pretty sure all the functionality is supported in htmx, but am looking for a reasonable example to jump off from.
  • f
    It seems like it is a form of lazy load, but I feel that is less than half the story...
  • f
    Any advice?
  • m
    sounds like you want polling:
  • m
  • m
    maybe on the table in question
  • m
    create a new endpoint (or you can look at the request headers from HTMX in the existing end point, if you point it at the same URL) and render just the table
  • f
    will read. Maybe I am over thinking it, but each row of the table will be driven by the specifics o fthe machine instance that it iis related to, and I need to understand how to relate that polling to the specific enquirey of the AWS API, along with getting a qucik intial page load and timely updates in due course.
  • f
    My semantic will be poor, not been playing in the web domain for long
  • m
    Do you want each row to update individually, or is the whole table updating, say, every 5 seconds, good enough?
  • f
    So as a rule of thumb would htmx look to seperately service each TD cell, or the entire table?
  • m
    Generally I always recommend staying as coarse-grained as usability allows
  • m
    the web is designed for coarse-grain hypertext exchanges
  • m
    (fancy way of saying "sending lots of HTML")
  • f
    Do you know of any decent examples that weild tables and similar use case?
  • m
    If you need more interactivity than that, it may be time to look at server sent events or web sockets
  • f
    I am happy to clone / break / fix until I understand it...
  • m
    Unfortunately I don't
  • f
    It doesn't need rich / responsive, just not clunky.
1...491492493...1146Latest