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... ❤️
@athlon Well, that's annoying! It's a frigging v- attribute that must support JS expressions out-of-the-box, but #Vue can't handle a simple boolean expected in v-show? :0530: What have you become, #VueJS...
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.
I'm pretty amazed with #Laravel+ #Vue+ #Inertia. In a nutshell, you don't have to write routes for your API endpoints and then routes in your frontend views, and then frontend methods to retrieve data and so on. You mostly work as if you were serving your server-side rendered views, write your models and controllers, and then you just pass the data as props to your Vue pages and components, and bang, done! I'm really having fun with my pet project. :)
I'll likely have some, say, free time from now on. So I can finally begin with some pet projects as an excuse to keep on learning, and yesterday I began a #Laravel/ #Vue project. Something I thought would be fun to do and I can use after (and if) it's done, a web app where I can keep track of my favorite music, fill data wiki-style, write reviews, and who knows what else. Some hours into that and I remember why I loved Laravel so much since I learned it a bit. :)
Over the past week, I've been working on a #Vue / #Firebase / #Bulma app that has been sitting in the back of my head for a decade. I'm using composables for every logical object. This would be sooooo much more code with the options API but I can't help but look at a 1000 line view and think that I could make things even better.
VitePress is a Static Site Generator (SSG) that takes #Markdown, applies a theme to it, and generates static HTML pages. Built on #Vue. #JavaScript#VueJS
When I started #Questlog the plan was to use the same tech stack as we use at work to use learnings from private projects for work and vice versa.
But Questlog doesn't have to be a single page app. And this annoys me. I have to go the extra mile for so many things that just should work.
I really think about completely rewrite the front end with #Laravel#Livewire instead of #Vue.js with #Inertia in between.
I would definitely have to think more to achieve some things I currently do, but the result would be a much faster and smaller page that isn't completely dependent on JavaScript. Most of the stuff I do would probably completely doable without JS these days.
Well, that fucking sucks. I just went into my o3 meeting with the boss and was told that I don't have a job anymore. If anybody is looking for an experienced #vue / #node / #php dev in the #Milwaukee area (or remote), let me know.