https://htmx.org logo
Join Discord
Powered by
# 🔥-django-htmx
  • m
    can't find anything on it
  • u
    You can achieve it with any backend. There's an example at htmx.org site: https://htmx.org/examples/infinite-scroll/
  • m
    ohhh, okay, thanks, but is there a tutorial/article about this anywhere?
  • v
    This last element contains a listener which, when scrolled into view, will trigger a request. The result is then appended after it. The last element of the results will itself contain the listener to load the next page of results, and so on.
    I don't know. You will want an html fragment page which renders some sort of object_list from your context dictionary. And on the last element, it will need to add to the final tag
    Copy code
    hx-get="{% your url tag pointing to the paginated view %}/?page={{ #something for next page number }}"
    hx-trigger="revealed"
    hx-swap="afterend"
    You'll want this fragment view to be included (with the % include % tag) in your full page view. The full page view should open / close the table tag and inside it should include the first page of a view following what I described above.
  • v
    @User
  • v
    That's how I think it might look, haven't done this personally though.
  • i
    Is there an example where someone does math with htmx? I need to update values in a database and then report the sum of those values. Ideally changing the value a clicking away (similar to https://htmx.org/examples/inline-validation/) submits updates to the database but I need the new data to be reflected in the sum elsewhere on my page.
  • m
    sounds like you either want to target that other area using 
    hx-target
    or potentially use an out of band swap to target it
  • i
    I'm reading up on this now. I'm interesting is solution 3 here: https://htmx.org/examples/update-other-content/ as a potential option
  • u
  • i
    I have a question about using alpine.js and htmx in a django app. I'm looping through an x-for in alpine and want to pass an alpine variable into x-bind:hx-vals = "{'myVal': 'My Value'}". Can this work?
  • i
    OK...figured this out. It does work...but requires a bit of parsing:
  • i
    :hx-vals="'{' + '\"' + 'myVal' + '\"' + ': ' + '\"' + alpine_variable + '\"' + '}' "
  • s
    Doing math with htmx.... Htmx is declarative like html. You can do math with a programming language, but htmx is a markup language.
  • i
    absolutely!. I'm thinking more along the lines of... user updates value in table >> POST request to Django >> update database and update new sum >> send response back to front-end
  • u
    The view that call all those operations (update database, update new sum, etc.) should return the HTML element that contains the sum value with the updated value (new sum) so that htmx can swap it in you current page.
  • u
    Django fellows: are you using Django Crispy Forms with htmx? Any issues? Tips?
  • u
    Yes, I do use it. No issues
  • u
  • u
    you basically pass certain htmx props through the form class
  • u
    Ow. Was looking for a more "templaty" solution.
  • u
    Yeah I understand. Mine is hacky 🙂
  • u
    Overall id say the experience with htmx and crispy forms is good
  • v
    Hmm, this is the exact use case. You just use htmx to post to a django view which handles the post request and returns the value (or rendered html fragment). all the request/response / math / db stuff is going to be in the view side. If you're using class-based views, this one is probably more straightforward as a regular old function. You can start with hx-post and hx-target on the htmx side 🙂
  • v
    which of these parts are you hitting a wall with?
  • v
    Oh, and maybe hx-include 🙂
  • i
    I’m just trying to wrap my head around an example of this in Django. I’ve seen the example on HTMX.org but it’s obviously missing the Django side of that. That’s what I’m missing (I think)
  • u
    You shouldn't think about the technology. Think about request and HTML responses.
  • i
    Cool. I appreciate the nudge. I’ll try to revisit them separately. I’ve nevertheless learned a lot by see Django specific examples which handle htmx request/response examples.
  • u
    On htmx, requests always starts on HTML (AFAIK). Django HTML responses are a View thing. It's almost that simple.
1...456...100Latest