Diving back into a project that used Vue and it seems to be throwing an error when I add a data- attribute to a HTML element. It's a static string which I use for something else.
Spent a bit of time early this morning to knock out the most basic vector editing features in my SCI0 pic editor. The SCI0 pic byte-code is very terse; it doesn't even have closed polygons, just lines that happen to touch each other when rendered to the frame-buffer.
I'm sure this whole UI layer will need a refactor soon, but its definitely another step in a "useful" direction. Just a few core features left before a "beta" is viable.
This project is actually a byproduct of another big thing I'm working on.
Currently, I use YNAB for budgeting, but I've been putting sustained effort into getting my data out of the cloud and self-hosting everything.
I started researching options for budgeting software, and I really couldn't find anything I liked or that felt like it had enough features.
I decided, then, to just whip up something in Excel... which led me to the discovery of Office.js and the ability to build Add-ins for Excel using web tech.
Thus, vue-excel was born.
I may eventually release my budgeting tool for Excel, when it's feeling a little more mature and stable. Stay tuned... ❤️
After a bit of playing with #FastAPI, I feel like it's really, well, API-oriented. You can have templating of course, but it's just a liiiittle clumsier than returning JSON (e. g., you need to manually inject the request into it).
So I'm not entirely sure if I should stick to my original plan of mostly rendering HTML and using #htmx, or if I should go with the framework flow and make a #Vue app. Probably the latter TBH.
@art_codesmith got it. Got it. Yeah, I haven't had the opportunity to dabble with a native async framework before, something I also want to try. You might want to check out some of the ones listed on https://github.com/sponsfreixes/jinja2-fragments like Quart or Sanic to get a feel of how they use templating.