https://htmx.org logo
Join Discord
Powered by
# 🔥-django-htmx
  • r
    Also yeah settled on "/thing/index.py" for base routes, but I might switch over to that "/thing.py + /thing/*" method you've described in darkstar.
  • r
    Retrospect is 20:20- index.py is more organized, but your method seems more intuitive.
  • b
    I'm trying to do the Real World app in it to shake out any issues.
  • b
    I did have an 
    index.html
    file to be the root template but I've just changed that to 
    index.py
    as then we're consistent.
  • b
    Part of me wanted 
    /path/index.py
    to handle the 
    /path/
    URL. But then I realised I could have 
    /path.py
    instead and still have things under 
    /path/
    . It actually seems to work, which is a nice surprise.
  • r
    Yeah.
  • b
    And it now has a whole 1 (one) star, which makes it officially my most successful piece of open source. 😀
  • b
    (though I did have the top 15 vim plugin about 18 years ago)
  • r
    honestly it's great dude to see people such as yourself on the starlette / fastapi stack. I've always found the relationship of fastapi to be pretty funny. It's the perfect example of hacker news hype putting the "branded verison" overtop of the original.
  • r
    but tbh, whatever grows starlette, it's all good.
  • r
    And to be fair, there's been a large number of usability improvements that may not have made it into starlette without pressure from the fastapi folks.
  • r
    As much as I love the starlette team keeping crap out of the framework, it's a fine balance.
  • r
    recent example:
  • b
    Starlette does seem like it's all been well thought through. It's interesting to see various FastAPI-like things start to pop up (Starlite, Xpresso). The idea with Dark Star was to get close to something PHP-like (template and code together) but being able to have all the modern magic of ASGI if you want it. If nothing else, I've finally managed to play with the 
    ast
    module, which I wanted an excuse to use for a while.
  • b
    I think it should work well for htmx. Want to ship a small piece of HTML to the browser? Just stick it in a file.
  • r
    Yeah. It's been my experience thus far as well.
  • r
    Funny thing, I toyed with Go recently, first thing I implement is always file-based routing. Go as a platform is really attractive to me (single binary deploys).
  • r
    the AST is super flexible, so you can get pythonic, brace-less style out of Go.
  • r
    But just couldn't get around the inconveniences of not having optional parameters.
  • r
    All the solutions just add so many extra lines (optional parameters, config structs, etc).
  • r
    My libraries are sooo much shorter with optional/named params available in Python.
  • r
    I really hope they reconsider these things for Go 2.
  • b
    Well it looks like we have #941388608290574336 now.
  • h
    Hello, I've created a quickstart repository on github with instructions which includes Django, HTMX and Tailwind CSS. It is pre-configured and has instructions to get you guys up and running very quickly. https://github.com/code-kasha/htmx-dj-tw-start
  • b
    Tailwind has a stand-alone CLI these days. I like that for when I don’t want to do the full npm dance. (It does stop you using other Tailwind plugins though.)
  • b
    Great idea! Thanks! Is there a chance to get a full standalone, which does not require npm?
  • h
    well, what we do with npm here is, get tailwind and build it via the classes in our html file
  • h
    it would still work if you just include a cdn of tailwind and htmx
  • h
    but you will be limited
  • b
    I often develope for offline systems on local servers, and always wanted to give tailwind a shot, but so far bootstrap is just so easy - only 2 files to copy.
1...474849...100Latest