3 ms·
You have built a beautiful TUI, hats off. Having that said, however, if feels like a missed opportunity for this project to use an SQLAlchemy-based database ba
by mrusme 2y ago
You have built a beautiful TUI, hats off. Having that said, however, if feels like a missed opportunity for this project to use an SQLAlchemy-based database backend over the more simplistic and widely supported ledger [1] format. While I understand that the your tool might not want to leverage the full complexity of a double-entry accounting system, as a friend of plain text accounting [2] I would have preferred a format that I can alter with existing tools, in order to be able to integrate _Bagels_ into an existing workflow.
Nevertheless, the TUI looks very clean and shows nicely how powerful the Textual application framework is.
[1] https://ledger-cli.org https://ledger-cli.org
[2] https://plaintextaccounting.org https://plaintextaccounting.org
- globular-toast 2y agoThis was my first thought too. Looking at the code it seems pretty tightly coupled to SQLAlchemy right now, but I imagine this could be replaced with a generic repository with a (probably read only) ledger backend to complement the SQLAlchemy one.
- withinboredom 2y agoGod. Please no. I hate double-entry accounting. I fiddled with Bagels for a bit and really like how simple it is to keep up to date. I don't need non-sensical accounts like "accounts receivable" and stuff like that. That's for my accountant. For me, I just need a way to keep track of the money. That being said, I don't care too much about how it does things under the hood.
- globular-toast 2y agoYou can do whatever you want with your own accounts. I don't have anything like an "accounts receivable" in mine.