[EMAIL PROTECTED] writes:
> If auto-fill as you describe was implemented, I would assume that
> would lessen the need for 'recurring transactions'
> i.e. automatically generated transactions that happen
> every-so-often. Would 'recurring transactions' still be an
> intersting feature to many people, or would it be a pretty much
> boring?
For me at least it's interesting. Recently I've been thinking about
this a little more (and filling Bill in on some of the old discussions
since he's only recently joined the list).
I'm trying to get an idea of what the "full blown" concept might look
like, and then see how a subset of that can be defined that's
relatively easy to implement so we can go ahead. I'll write something
up when my thoughts have settled and we can hammer on it. I believe
we have nearly all the infrastructure we need now for a useful level-0
implementation, so it shouldn't be a big deal.
Before that, though, I'm implementing the "guile listener" that
Christopher and I discussed a while back. I started in on it a while
ago and never got back to it, but now that I've had time for it to
mentally percolate for a bit, unless I'm overlooking something nasty
it looks like it's going to be easy, and aside from other potentially
cool uses, it could be a *big* help for debugging. I should have an
initial patch in the next day or so.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
