You are browsing as a guest. Sign up (or log in) to start making projects!

3h 15m 17s logged

Devlog

I found another way to hide the fuel stat when it isn’t useful for a particular type of car: the HTML hidden attribute.

At first, I thought I should add or remove the element hidden, but that turned out to be more complicated than I expected. I think using hidden is still a cleaner solution but I still using templates files.

While working on the dashboard, I wanted to add units like km, L, and % to some values. Instead of handling that in Python, I added another div with some margins and, in a few places, used flex so everything stays on the same line without adding more backend logic.

  • Added more page changes thru HTMX (nearly all pages use it).
  • Creating a new car now refreshes the page.
  • when an error occurs, I use HX-Reswap and the HX-Retarget response header (when creating new car as proof of concept).
  • Added HTMX transitions to the OAuth2 settings page.(all pages have transitions)

What to do before the first release

(Mostly a checklist for myself 😅)

  • Content-Type checks.
  • Scenario and snapshot system support in the dashboard.
  • Main showcase page.
  • Finish the remaining documentation.
  • Two READMEs: one for the main repository and one for the companion app repository. I’m thinking about having one technical README and another one that’s easier to understand for people who don’t code.
  • Better error handling in the dashboard. Right now, most errors are just displayed as plain text instead of being part of the page.
  • deploy updated version on nest

I wanted to add a video but MacOS made me a half gig and I don’t think stardance would handle

0
44

Comments 0

No comments yet. Be the first!