design documents?

Derek Atkins warlord at MIT.EDU
Sat Mar 29 11:40:27 EDT 2008

I'm afraid that really there are no good design docs.  Certainly
nothing coherent.  Many times there are email discussions when a
feature is being created, but nothing really gets put down for
posterity in the source tree.  Unfortunately I have to say the
the design doc is the source code.


Quoting Ross Boylan <RossBoylan at>:

> Are there any somewhat current design documents?  I'm not having much
> luck finding them.  I'm poking around, mostly in hopes of recovering
> some data, and am trying to find the format of the .log files (more
> details on the user list).
> Here's what I tried:
> got trunk from svn.
> README says:
> Also read
> 2. Several of the directories under src contain files called design.txt
>   which explain many aspects of GnuCash's design. Read those.
> The  wiki says to reading HACKING, which says to look in src/doc/design
> directory.  The files  there seem to either have prominent warnings that
> they are obsolete, or to have no substantive information.  They may be
> designed for use after a build process (which makes them a little harder
> to use), but basically they seem obsolete.
> find reports 3 files named design.txt.  I try src/engine/design.txt,
> which says it is  "becoming obsolete" and refers me to src/doc/design,
> already self-identified as obsolete.
> Both doc/ and src/doc seem to have scraps of stuff that's relevant.
> doc/projects.html seems like an overview, but it refers to versions 1.6
> and 1.7.
> Thanks.
> Ross
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at

       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL:    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available

More information about the gnucash-devel mailing list