>> A tutorial would be just the right thing. Several have been >> started, but as far as I know none have been finished. I'd >> be happy to co- author one if anyone feels like cobbling >> together a book -- this probably requires getting 2-3 people >> to hammer out a structure and then divide up responsibility >> for individual sections. The PDL_BEGGINING_BOOK CVS tree is >> an interesting start but now unfortunately somewhat out of >> date... >> >> My guess is that we can't get a book written with the same >> freewheeling contribution style that works for the software >> in general -- the reason is that it takes more effort and >> discipline to write English than to write small modules of >> code.
How about using a wiki for writing the book? I noticed that the sourceforge page seems to have some sort of placeholder for a wiki. Use of a wiki would allow many contributors to generate the basic content of the book in their areas of experience/expertise. Then, the text could be wrapped up into the "book" itself with figures, editing and proofing. I would recommend that version control be used on the wiki and required sourceforge userID for submission (at a minimum). I've worked through chapters 1-5 of the "PDL Book" and except for some missing data sets and changes in slicing syntax, the text mostly worked for me. I have not been able to work through chapter 6 due to missing modules, other prerequisites, and a lack of time on my part. --Chris
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
