scheduled transactions since last run vs cash flow report

[aperomsik@mail.com]

Hi Josh,

Some time towards the end of June I managed to build out of CVS and
play with schedxactions a bit. Things are looking pretty cool.

In the Since Last Run dialog, I like the fact that I can select just a
few transactions and create those. For planning purposes I expect to
have all my transactions set to create 60 days in advance, but I don't
expect to actually enter them that far in advance. Therefore, it would
be more useful if the since-last-run list was sorted by date rather
than grouped by parent SX.

Beyond that simple detail, here's my pipe dream for extending the
functionality of the since-last-run dialog.

  - Upcoming transactions sorted by date.
  - Amounts of any upcoming transaction can be edited independently of
    the parent SX even without entering it for real yet.
  - Additional columns show the hypothetical balances of the affected
    accounts as of each transaction. The tricky part is accounting for
    "real" transactions already in the register for dates in between SX
    dates.
  - Then I can pick a few transactions from the list and hit Next as
    today to instantiate them.

What do you think? You probably will say that this isn't what
since-last-run is for. I don't care if this is integrated the existing
since-last run, or replaces it, or provided as an alternative entry
point into the SX instantiation UI. But with something like this I
will be well on the way to dropping the OpenOffice spreadsheet which I
currently use to manage my cash flow.

[Actually, that spreadsheet has completely replaced scheduled
transactions for me at the moment, because last weekend we decided to
give up on Quicken and move to Gnucash 1.6.5. More on that in a
separate email after I look for some issues in the archives.]

I know there are plans to eventually have some kind of cash flow
report... I just want start some discussion, and to make sure whatever
that turns out to be will be "live" and somewhat editable, not just a
dumb report.

-- 
Aaron Peromsik <aperomsik@mail.com>