Re: Generic importer:QIF

Chintan Agarwal [EMAIL PROTECTED] writes: Thanks for that information. I could not find the declaration of Transaction structure(or its un-typedefed form) per say but from the functions in the file, could gather the variable types present. Like I said, src/engine/Transaction* -- the structure

Re: Generic importer:QIF

Thanks for that information. I could not find the declaration of Transaction structure(or its un-typedefed form) per say but from the functions in the file, could gather the variable types present. I think that for QIF importer, we could have a simpler structure, akin OFX importer wherein the

Re: Generic importer:QIF

Hi¸ Quoting Chintan Agarwal [EMAIL PROTECTED]: Thanks for that information. I could not find the declaration of Transaction structure(or its un-typedefed form) per say but from the functions in the file, could gather the variable types present. I think that for QIF importer, we could have a

Re: Generic importer:QIF

Huh, sorry, I didn't see Derek's answer before writing my own. @Chintan: If I've said anything different from Derek, please ignore my remarks. Derek's answers are (as usual :) more correct than mine. Christian Am Sonntag, 24. Juni 2007 21:21 schrieb [EMAIL PROTECTED]: Another thing to keep in

Re: Generic importer:QIF

Am Sonntag, 24. Juni 2007 20:22 schrieb Chintan Agarwal: Thanks for that information. I could not find the declaration of Transaction structure(or its un-typedefed form) per say but from the functions in the file, could gather the variable types present. That is intentional. We don't use

Re: Generic importer:QIF

Quoting Chintan Agarwal [EMAIL PROTECTED]: Can the code in /src/import-export/import-backend.c and other files in the same folder be used for mapping a parsed qif file? As far as I understand, this is the generic framework that we want to use for all imports. Is my understanding right? Yes,

Re: Generic importer:QIF

Hi Chintan, please remember to CC gnucash-devel on all replies. Quoting Chintan Agarwal [EMAIL PROTECTED]: Thanks for the prompt reply. So importing from any format now essentially involves parsing it and passing on the parsed object to the generic importer. Yes, exactly. The front-end, of

Re: Generic importer:QIF

The OFX importer is proving very useful in understanding how to write a qif importer with the given requirements. There was another question I had. This pertains to the variable type Transaction which is required by the gnc_gen_trans_list_add_trans function in import-main-matcher.h. Due to the

Re: Generic importer:QIF

src/engine/Transaction.* -derek Quoting Chintan Agarwal [EMAIL PROTECTED]: The OFX importer is proving very useful in understanding how to write a qif importer with the given requirements. There was another question I had. This pertains to the variable type Transaction which is required by

Re: Generic importer:QIF

Chintan Agarwal [EMAIL PROTECTED] writes: frequent occurrence of the word Transaction, I could not successfully find the definition of the data-type(=Transaction data-type). If you could point src/engine/Transaction.[ch] You will generally want to familiarize yourself with the Engine, as

Generic importer:QIF

Can the code in /src/import-export/import-backend.c and other files in the same folder be used for mapping a parsed qif file? As far as I understand, this is the generic framework that we want to use for all imports. Is my understanding right? Thanks. -Chintan