On 1/20/2012 7:23 AM, Matthew Kenworthy wrote:
There's been some traffic about the status and location of the PDL
Book, so this is an attempt to summarise what's been going on:
The PDL Book is in a git repository, which you can currently look at
with your browser at:
http://pdl.git.sourceforge.net/git/gitweb.cgi?p=pdl/pdl-book;a=tree
The top level of the repository contains the file 00README.pod, which
gives more details on how to get a local copy, and how to get write
access and contribute to the Book. Please read this through to get a
good idea of what's going on:
http://pdl.git.sourceforge.net/git/gitweb.cgi?p=pdl/pdl-book;a=blob;f=00README.pod
...and the list of chapters and ordered section is in PDL/Book.pod:
http://pdl.git.sourceforge.net/git/gitweb.cgi?p=pdl/pdl-book;a=blob;f=PDL/Book.pod
Thanks to the efforts of several people on the Perldl list, we have a
relatively complete set of PODs and figures that make up a functional
book! The PDF version of the book is running to 159 pages with the
included figures. I'm not sure where I should put a live copy for
others to read... Chris, suggestions?
I did a make_book.pl and took a look at the generated
PDF output. It was a little confusing since there are
no chapters. Maybe it would make sense to modify the
program to generate individual chapter PDFs. They could
always be concatenated for the full book.
Also, a couple things that the book will need:
- Table of Contents (maybe Pod::TOC can help)
- An *index* (see Pod::Index)
TODO list:
Import/write sections on TriD, Complex numbers, Threading, Transform,
Pthreads, Proj. Do we want a chapter on Proj?
Proofread the chapters and check that the examples work, and fixing
many links in the docs.
And add X<> entries for index generation...
Work out directory structure that is suitable for PDL distribution and
for others to contribute.
How is this coming along? Right now there are all
sorts of different names and cases. Maybe this
could be done before the push for general edits
and feedback?
My goal is to start reading the chapters and cleaning them up into a
consistent flowing book. If we stopped additions *right now*, we then
have a minimally useful book. The rest is making sure that the
demonstration files are easily accessible for interested users.
Thoughts?
It is starting to shape up. The "make it work like a book"
is going to be the next important step. Well, I'd better
get cracking on my promised chapters.
--Chris
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
