Derek Atkins <[EMAIL PROTECTED]> writes:
> All you need to do is mark the time at which an account was last
> saved. Next time you load it into GnuCash, it processes all the
> 'timed' transactions that occurred between then and "now". You really
> don't need (or want) asynchronous events here. "Cron" and "at" are
> superfluous. It's not like we need GnuCash to start up on its own and
> tell us a bill is due. ;)
I disagree. That's exactly the kind of thing I want it to eventually
be able to do. As another trivial example, you may want it to
periodically (as in, even if you're not there), collect some stock
prices, compute some results, and notify you if some criteria are met.
The solution's not that hard. I had originally hoped to just augment
"at" to support a few extra features you'd have to have to be able to
solve the problem cleanly, but I've been met with silence from the
developer, so I'll probably have to do something else. I may just
take the at source and create a tool that'll do what I want. If I do
it right, then other programs could use it too. It's silly for every
tool that needs to do this kind of scheduling for the user (i.e. plan,
via pland, gnomecal, ical, etc) to have to start from scratch. Of
course, this is all presuming I have the time to get it done, and
presuming that in the end it turns out to be a good idea.
Don't worry, though, if this works out, I expect to make this
functionality optional. You won't have to install anything extra to
be able to use gnucash, but you might have to install something if you
want to use asychronous events.
> I hope we're not over-engineering a solution to what (to me) is a set
> of simple problems: Installment Loans and Depreciation.
Well, I'm happy with simpler short-term solutions, but my ideal
solution would be something like what I described.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
