[EMAIL PROTECTED] wrote:
> If you personally do not want to record price data, that is your
> prerogative. The engine doesn't care. It'll store it if you ask it to.
Okay. I was not aware that it was currently used to do so (don't get me
wrong, I was not trying to say it should; I was just making an
assumption that it currently was not)
> You raise a very interesting point: someone (e.g. you) may want to
> merge, on the fly, gnucash data stored in a file with data from the
> outside world, e.g. prices sucked down off the net. There are any
> number of ways to do this, and at least some of the ways require
> no changes whatsoever to the engine, and these same ones might take
> only a small impact to non-engine code.
>
> > Matt wrote:
> > <stuff about raising rabbits clipped>
>
> I apologize, but I completely fail to understand what you are getting
> at.
>
> > <transaction editor stuff clipped>
>
> And of course, I completely fail to understand why I need a new engine
> as a result.
I don't think I was suggesting changing the engine itself; rather, this
particular issue sprung up as a result of how stock information
(buy/sell in particular) is currently represented in the engine. The
engine can handle either representation (and more), if I understand you
correctly. If retroactively altering the information contained within
the transactions is a bad thing (such as one of the possibilities of
dealing with stock splits would suggest), then it might be better to
adopt a different standard of representing the transaction -- one that
is not vulnerable to the vagaries of stock splits.
Concerning the higher level API stuff I was getting at -- I will demure
for now until I have a better understanding of the engine code. Although
the engine itself can store many things, I need to learn how the
meanings of the values can be extracted for a particular entry. This
could be a simple, complex, or nonexistent thing; I will learn shortly.
Ultimately, I would like to see the end user be able to craft custom
transactions and harness the engine -- this is what I was getting at
with the "transaction editor" idea -- not editing the values in a
particular transaction, but constructing a new transaction template for
use by the engine. Apologies if this sort of thing is already in place;
I am not aware of it if it is.
BTW, in case I have mangled the tone of my conversation in these emails
-- I am completely excited about gnucash and the opportunities it
offers, from both a usage and development perspective. It is a nifty
piece of software; my point was not to criticize the effort it
represents.
I look forward to future collaboration.
Matt
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
