[1] https://www.xmlui.org/ [2] https://docs.flightphp.com/en/v3/
Hyperflask – Full stack Flask and Htmx framework
131–140 of 160 posts
Re: Hyperflask – Full stack Flask and Htmx framework
#132Some interesting concepts: - Components: https://hyperflask.dev/guides/components/ - Bundling view and controller in the same file: https://hyperflask.dev/guides/interactive-apps/ I think these may be footguns though. Components for example are just a regular macros under the hood. Why not use macros then? I'm also curious about the choice of Flask. I started with a similar approach for /dev/push [1], but ended up mo…
Re: Hyperflask – Full stack Flask and Htmx framework
#133Hello, author of hyperflask here. I'm happy to finally announce this project as I've been working on it for quite some time. I made an announcement post here: https://hyperflask.dev/blog/2025/10/14/launch-annoncement/ I love to hear feedback!
I’ve been looking for something like this but backend agnostic (library rather than a framework) because we’re already about a million lines deep into a Django project. Anyway to lift this up into something that I can just mount into a Django app?
Notable sub-projects that could be used with Django:
Re: Hyperflask – Full stack Flask and Htmx framework
#134I have been using htmx to build a web app and came to the conclusion that it is a dead-end. The main problem is that the state of your frontend application is in the URL. This is not flexible enough for modern UI where you might have many different zones, widgets, popups, etc. that all need their own local navigation, activation states etc. Putting all of this in a single global url is extremely hard. Designing your…
Re: Hyperflask – Full stack Flask and Htmx framework
#135Re: Hyperflask – Full stack Flask and Htmx framework
#136Earlier quoted context omitted.
> The main problem is that the state of your frontend application is in the URL. There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the…
> There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the URL. > It's not a black or white, one actually has to think about what the appl…
Something has to do this in an app regardless of what UI framework you're using. Deciding where a particular piece of state lives is fundamental to web development, and yes, URL/session/cookie/database are all valid options depending what kind of state you're storing.
Re: Hyperflask – Full stack Flask and Htmx framework
#137Earlier quoted context omitted.
> The main problem is that the state of your frontend application is in the URL. There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the…
> There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the URL. > It's not a black or white, one actually has to think about what the appl…
Notably, none of this is incompatible with React/Vue where you need it.
Re: Hyperflask – Full stack Flask and Htmx framework
#138Earlier quoted context omitted.
It's a dead end for your use case, let's be very clear about that. And it's funny that you think anything about React and/or Vue is 'trivial'.
Surely you’re not saying the frameworks famous for ui = f(state) actually suck at managing state…
Garbage. But effective devrel.
Re: Hyperflask – Full stack Flask and Htmx framework
#139I have been using htmx to build a web app and came to the conclusion that it is a dead-end. The main problem is that the state of your frontend application is in the URL. This is not flexible enough for modern UI where you might have many different zones, widgets, popups, etc. that all need their own local navigation, activation states etc. Putting all of this in a single global url is extremely hard. Designing your…
What exactly are you talking about, for React? What provides "a state store"?
Re: Hyperflask – Full stack Flask and Htmx framework
#140Earlier quoted context omitted.
There isn't any real inherit project structure. Opinionated frameworks often work better with multiple people involved.
Isn't every project an ad hoc opinionated framework? You can do code reviews etc to get some alignment and not have everyone working against each other.