Bug 103181: not-monthly repayment schedules not supported in Mortgage/Loan Druid

David sunfish62 at yahoo.com
Tue Jan 14 10:25:11 EST 2014


As a longtime user, I can tell you that there will be a huge cry of thanks from the user base if you can get the mortgage calculator working better. I know I am not the only user who has either abandoned the scheduled mortgage payment altogether, or who has to change every created transaction after the fact because the calf's are off.

I would ask you to consider checking first on whether you can create a "balance as of date" function, as it seems many mortgage complaints originate from the fact that GnuCash can't do this. With such a function, users would be able to prepayment their loans and GnuCash would still be able to calculate and allocate correctly -- something it cannot currently do.

I've been told this would be complicated, but I toss it out with hope...


From: John Ralls <jralls at ceridwen.us>
Sent: Tue Jan 14 06:57:59 PST 2014
To: alessandro basili <alessandro.basili at cern.ch>
Cc: GnuCash development list <gnucash-devel at gnucash.org>
Subject: Re: Bug 103181: not-monthly repayment schedules not supported in Mortgage/Loan Druid

On Jan 14, 2014, at 5:22 AM, alessandro basili <alessandro.basili at cern.ch> wrote:

> Hi John,
> On 1/13/2014 5:46 PM, John Ralls wrote:
> [...]
>> We're not terribly concerned about API changes, especially in the
>> gnome and gnome-utils directories. Just make sure that if you do
>> change a function's signature that you check for and fix both C and
>> Scheme callers.
> I do not know Scheme (shame on me! :-)) but I guess checking for the
> call wouldn't be an issue.

So many languages, so little time. ;-)
The function names are the same as the C ones except that words are separated wit '-' instead of '_'.

>> We also need to separate the computations from the
>> GUI code in those directories. You don't have to do that yourself,
>> but please keep the goal in mind. 
> I'm afraid I haven't fully understood this point. Could you elaborate?


Most current GnuCash code does not separate the controller and view code. We need to fix that.

>> If you can, please add unit tests
>> to any functions you alter significantly.
> I would follow recommendations and already existing examples in order to
> provide some level of testing.

The existing examples aren't all that good, especially outside of src/engine and src/libqof/qof.

John Ralls


gnucash-devel mailing list
gnucash-devel at gnucash.org

More information about the gnucash-devel mailing list