siggy version 0.3 released!
As promised, the brand new 0.3 version of siggy is out 🙂
You can get the source code and package at garage, and it has also been uploaded to the extras-devel repository. You can check the source code from its git repository as well.
When developing this version, my idea was to add some way to get information from the data stored in the database. So I thought of two views. One of them would be a statistical view, where I could check how I’ve been evolving during a period of time, showing totals, average values, etc.
The other view would be a kind of chart representing the amount of money spent during a period in each of the items defined in the application.
What do you think? Could this be useful to you? 🙂
Unfortunately, the next mayor update is not out yet, so the limitation to move the package from extras-devel to extras-testing is still there. Anyway, this can be seen as an advantage 😉
For the upcoming 0.4 version, I have planned a couple of features requested by you:
- The first one is adding support multiple accounts, just in case someone wants to handle more than one of them.
- The second one is adding to the expenses in the database some kind of unique id that would allow synchronisation with a centralized service/database. This one opens a new and really interesting functionality for the application: it could be used by workers from a company to write down their work expenses. Periodically, the workers might sinchronize their expenses with the central server, so they are automatically queued to be paid as allowances. Sounds cool, doesn’t it? 🙂
- If I have enough time, I will also add password protection to open the application
So, why the delay in the mayor update is an advantage? All these new features require changes in the database tables, which means problems for those who have started to use the application using a previous vesion. So, my advice is: test the application as much as you can, report bugs, patches, translations, etc, but don’t start to use it regularly yet. Wait a bit more. I’ll try to have the next version ready before the upcoming mayor update. This way, when the update is out, you’ll be able to install the new version without migration problems 🙂
Anyway, if there’s someone who wants to start using it asap, just tell me, and I’ll provide a script to update the database together with the new version.
I’m eager to get feedback from you!! 🙂
(Update: I put https URLs instead of http. Sorry! Should be fixed now.)