https://bugs.kde.org/show_bug.cgi?id=455428
Nikita Krupenko <krne...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |---
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
--- Comment #2 from Nikita Krupenko <krne...@gmail.com> ---
Hi Stephane,
Sorry, I've missed notification for your response.
As read from the documentation, we have two types of schedules: template and
non-template. I think both are useful, see my arguments below if you are
disagree. The problem is that if one need to create a specific type, the only
way is to change the required type in options before scheduling an operation.
Also if one will change options to create template schedules, Skrooge will
convert all schedules to template ones - not what I would expect.
To convert a template operation to a non-template one, the code should find the
latest operation linked to the schedule and make it to be the reference to the
schedule and remove the template. If we have only a template (and no operation
linked to a schedule yet), then the conversion isn't possible. I've implemented
the changes, see MR 34.
It seems that there was (unknown to me) reasons to have only template schedules
and treat non-template ones as some legacy, but I think we better allow to have
both types.
I think we need templates when we're going to add additional operations with
same category/payee/account/etc in addition to operations, that are added by
processing a schedule. An example: we pay each month 10€ for mobile
communication and receive some minutes of mobile calls and some megabytes of
mobile internet. We can schedule such payments. But sometimes we can have
irregular additional expenses for mobile communication:
- a payment for additional minutes or megabytes of mobile internet;
- a payment for roaming if we're going to use the mobile phone during a travel
to another country;
- a payment for some international calls.
Here a template could be useful and we can use it to quickly add an additional
operation for irregular expenses.
For some operations it will be unlikely that additional irregular ones will
arise and we don't need to create useless templates in this case.
As an example of such operation one could see a stock-based compensation from
an employer. If a person receives a grant, it will be vested with some regular
period and the amount of shares is finite and there shouldn't be any additional
operations - therefore we don't need any template here.
Another example could be utility payments. For example, one could pay for
electricity each month and it's unlikely that there will be any additional
payments. The payment could increase over time due to inflation and with
non-template schedule if we change the amount in the latest operation, the next
created operation will be with this new amount, which is useful.
--
You are receiving this mail because:
You are watching all bug changes.
