I combined Nicolas's and Jarl's documents into a single one. It is in the piper-website module, *NOT* the piper module. I think that we should *NOT* put docs in the piper module for now, because we don't have anything formalized, and scattered bits and pieces of documentation may be more than users can manage. Plus, with images and all, these docs can add a bit to the package size. Once we have a couple complete manuals, they can go in the piper module. I think that we should call this document the "Piper Developer's Manual" And I have split Nicolas's and Jarl's contributions into 2 parts: Goals and Design. I did not attempt to do as Jarl said: "every subsection should start by a 'what' and defined by a 'how'", because there is little overlap between what I've got (IOW, Nicolas didn't write "The purpose of the BL is..."). Oh, it is attached. Cheers. Jeff -- J.W. Bizzaro jeff at bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "All those scientists--they're all alike! They say they're working for us, but what they really want is to rule the world!" -- Angry Villager, Young Frankenstein -- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://bioinformatics.org/pipermail/pipet-users/attachments/20010218/ff0b69b0/piper-devel-manual.html