Welcome back

[Derek Atkins]

linas at linas.org (Linas Vepstas) writes:

>> A book-merge: function is an excellent idea. I'll get that done.
>
> OK, let us know how this goes.  Although we could add support for lists
> and trees into qof (to handle the lists of splits and the account tree)
> I'm not sure that I want to burn the brain cells right now to figure out
> the 'right' way of doing thiis, not just yet.   By contrast, the
> book-merge-per-object call seemed like a simple catch-all.

I agree.  I think you can safely ignore the lists in most objects
(except, perhaps, transactions) as those objects will get merged into
the book later.  For example, you don't need to worry about the
Account SplitList, because that's really "controlled" by the Splits
themselves.  When you merge in the splits you get their "parent"
account just fine.

The only potential issue I can imagine is merging transactions -- you
somehow need to detect that what you're merging has fewer splits
(e.g. if you change a transaction and remove splits).  I'm not sure
how this can be done easily....

>> > OK, I'm still jet lagged.  What's you sourceforge id?
>> 
>> codehelpgpg
>
> Done.  Please note that I currently keep qof and gnucash in sync
> manually, and that this is a potentially error-prone process.  
> Let me know if anything looks funny.

-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
       warlord at MIT.EDU                        PGP key available