On Wednesday 22 September 2004 4:23 am, you wrote:
Neil Williams [EMAIL PROTECTED] writes:
I'll look into that. TBH, I'm not sure why it is calling OpenSP, except
that it is loading the current XML datasource files directly, without
user intervention and without using Guile/Scheme/GUI.
Neil Williams [EMAIL PROTECTED] writes:
Well, it shouldn't depend on the XML backend even if it's embedded in
the GnuCash tree.
Sorry, I wasn't clear. XML as data interchange, not as a backend. If it's
going to receive QofBook data from external sources, including pilot-link or
via STDIN,
Support for merging QofBook's with collision handling. The qof_book_merge code
works but there remain issues with the implementation in the GUI.
A test routine is included in the release.
The GUI code includes a Merge Druid that is wrapped around the Account
Hierarchy Druid usually called by
On Wednesday 22 September 2004 2:56 pm, Derek Atkins wrote:
AHHH.. Yes, indeed, XML is definitely suited to this. However your
code still shouldn't assume XML, because a user may want to merge two
PG databases together, or a PG and XML dataset, or an XML and SQLite
(once that's
Neil Williams [EMAIL PROTECTED] writes:
5. Problems with AccountGroup - although the new accounts are committed to the
original book and the book is restored correctly, the changed accounts don't
appear. I suspect this is due to incomplete support for AccountGroup.
Yea... AccountGroups
On Wednesday 22 September 2004 3:49 pm, Derek Atkins wrote:
Thank you for learning and doing the work! How can we keep you interested
in doing more work?
I've got plenty more I'd like to do with the merge and GnuCash - just for now
I need to give some time to other projects and certain
