On Sat, Nov 27, 2010 at 11:23 AM, John Ralls <jra...@ceridwen.us> wrote: > > On Nov 27, 2010, at 4:40 AM, Donald Allen wrote: > >> On Sat, Nov 27, 2010 at 5:23 AM, Fred Verschueren <f...@fremar.be> wrote: >>> Don, >>> >>> thanks for your advice and explanation. >>> I've done it the way you described and it took me 50 sec per year for one >>> account, so in total 25 minutes. >> >> Good. >> >>> >>> Nevertheless I think having the layout of the database can help making own >>> reports easy. >> >> Absolutely. I've already done my own report-writing outside gnucash, >> processing the xml file (with a python program; python has good xml >> parsing facilities in its library), which I reverse-engineered. Having >> the data in a database and the data-model documented will makes this >> sort of thing much easier and the code less messy. >> > > You do know that there are python bindings to Gnucash's internals in 2.3? No > need to reverse-engineer (well, maybe a bit -- the developer documentation > isn't that great).
Yes, though I haven't looked at it yet; thanks for the reminder. My python report-generating stuff was written a few years ago, long before the python bindings. When the new version is released, offering more and better choices than I had back then, I will re-visit this and use what seems most suitable for my report-generation needs. /Don > Regards, > John Ralls > > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
