-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calculated costs #6
Comments
Mmm, that could work, maybe combined with "piggy banks", a saving-money feature that's about finished. Let's say you want to buy expensive thing X. You could set a target date or a target period (x weeks/months/year from a certain date, repeating) so you would end up with something like you describe:
To make it useful, such a target needs fields like a target date, a repeat frequency (if relevant) and other things. Most importantly, you should be able to connect transfers (to a savings-account or another account). So, I move € 400,- to my savings account. Amongst the fields already present on this form is a field that allows me to select the target this money is intended for. The money is automatically added and associated to the target. If you set Firefly to remind you every week/month/year about the target, the reminder will disappear for the rest of the week/month/year (this in connection with the budgeting / monthly budget you mentioned). To fill in the car example. I need € 10.000,- in three years. This means about € 278,- every month. Firefly will remind you every month to save this amount. In three years, you should be on schedule. Firefly might even tell you you're behind or ahead of schedule. Is this about right? Did I get what you meant? |
Alright, so. A piggy bank needs at least the following information:
To make piggy banks repeatable (to save for a new phone every three years), we need more information:
Then we also need new object, a kind of "piggy bank instance". It should contain the bare minimum to store repetitions and keep track of the amount therein:
The rest of the information is taken from the piggy bank itself. Every piggy bank, repeating or not has at least one instance. |
…dded a new class (yet to be tested) and removed most of the "piggy bank"-implementation in anticipation of the ideas from issue #6. Fixed a bug in the default user seeder.
This is indeed exactly what I mean! Great work already! |
…an now be made "repeated" in a different form, viewed and edited; Firefly will properly trigger to make the "instances". Also the show-view is finished which doesn't do much but helps in seeing how it works. [skip ci]
…transfer. Also various fixes (see issue #6). [skip ci]
Still to do: save the changes to piggy banks (added 5, removed 10, etc) so all instances will update nicely when they are recreated. |
When having (large) costs, for example paying car taxes once a year, it would be nice to see how much of the monthly budget this will take. And thus how mush money we would need to set aside each month to cover the complete cost.
Another example could be: I want to buy a new smartphone every 3 years, how much money do I need to set aside each month to cover this cost.
This way you also have a "general" usage that should be the same every month and should allow you to pay for every (big) costs.
The text was updated successfully, but these errors were encountered: