Hi,
Welcome....
Quoting John Griessen <[EMAIL PROTECTED]>:
> Hi,
>
> I am a new user and probably a future testing/documentation contributor,
> and maybe even code. With a real object database inside, gnucash has
> big future usefulness. I'd appreciate suggestions for studying how to
> create an extension of transactions and splits to allow
> attaching/relating/linking
> images to them.
This idea has been mentioned before. Basically you'd need to make a
"table of images" and then reference the image from the transaction (or split)
kvp area.
> I have paperless office goals in mind, but also these kinds of
> objects/entities would be good for EDI, and for extending the whole gnucash
> concept beyond traditional financial boundaries and creating a cross-over
> between
> financial/transaction data, engineering design and part list data, and
> marketing
> research and promotional data. I like operating in groups that are small
> and
> relatively flat -- peer groups with no wage slavery going on-- so I like
> handling
> business data as few times as possible before it is where it needs to
> be for the next business process step. That's what motivates linking
> finance-engineering-marketing data as objects the Gnucash Query Object
> Framework
> can access.
>
> So what's a quick, (and hopefully not too dirty way), to link a receipt image
>
> to a transaction by minimally modifying the transaction engine?
> I'll start reading the source code under src/engine/.
I already suggested the straightforward way. Basically, you need to create
a way to import and image and store it in the database. Provide the image
with a GUID, a 'title', maybe some notes, and then the image data. To attach
the image to a transaction (or a split -- I dont know where the correct place
would be) you would just create an entry in the KVP that points to the image
GUID.
Perhaps a better solution would be to make the title be the KEY that points
to the image GUID -- instead of storing the title in the image itself.
That would allow you to have multiple images associated with a single
item:
/images/cheque-100 -> GUID{123456...}
/images/lading-102 -> GUID{234567...}
etc.
> Thanks,
>
> John
You would just need to create a few functions to make this simple..
And you could look at the contents of /images to get a list of all
the images attached to an object.
If you want you could even back-point the image to the object by putting
the object GUID in the image, but then you need to make sure both pointers
are always correct and updated (which may be an issue across period boundaries).
Hope I've helped...
-derek
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
