bounties

[Chris Shoemaker]

On Wed, Feb 08, 2006 at 03:04:08PM -0400, don Paolo Benvenuto wrote:
> Hi guys!
> 
> I'm putting bounties on some new gnucash feaures, namely:
> 
> - US$ 100.00 for adding to the general accounts tab the possibility to
> see the "actual" balances referred to a given date. It could be done via
> a text box to put in the upper right corner.

You probably know that these account balances as of a certain date are
available in the reports, and I'll also note that in a _very_ indirect
way you can certainly also see these account balances using the
'estimate budget' feature of budgets, since that's pretty much how it
works.

Also, the summary bar on the account-tree tab is supposed to give
summary values for a given accounting period.  But I agree that it
could be nice to see the per-account balances that contribute to those
sums.

David made a lot of convenient routines for adding columns to
tree-views, so this shouldn't be that hard.

A couple things to note, though:

1) For consistency with the summary bar, and so that it can re-use the
date entries, I don't think it should show the absolute account
balance at one date, but rather, the account balance *change* during
the accounting period.  Those two things are the same if your
accounting period starts before your first transaction, but you might
want to just see the balances for, say, the last three months, so I
think that's more useful.

2) New features are going into svn which is releasing 1.9 betas very
soon, but not the stable 2.0 until some months now.

I'll look at this after dinner.

> - US$ 100.00 for adding the possibility to present the report options
> before calculating the report. That'd be useful because with many
> accounts and many txns the account are generating in a very long time,
> and normally you have to customize the default settings in order to get
> what you want. There should be a flag control in the preferences, where
> the possibility to present the options before calculating any report
> would be set: "set reports options before calculating them", and all
> reports should obey this setting.

If I understand the problem, I think the best solution is to make sure
that every report has default values that won't result in a
long-running calculation.  Do you have a particular example or one
that doesn't?

-chris