On 1/22/2012 3:13 PM, Matthew Kenworthy wrote:
I've added a bookchecker program (a.k.a. a renamed
podchecker script with use lib (qw(inc)); in it to
use the slightly modified Pod::Checker::podchecker()
routine. It doesn't complain about the =ff or the
O<> pod syntax additions from pod2pdf.
That's good to hear - but does this add another dependency to most people's
Perl, or is it in the perl core?
It is a quick hack at the moment for use by
contributors. If we are going to make a
distribution on CPAN for this, it might,
logically, include a module to handle the
book pod stuff---one stop shopping.
Also, we might be better off to implement our
own version of pod2pdf for the PDL::Book activity.
The limitations of the existing pod2pdf are
somewhat artificial and might be addressed by
coding it up ourselves.
This sounds very good - can this be done before the release?
Probably not. I'm thinking this first release
will be doing good to get out the door with
content. :-)
NOTE: We could save a lot of space in the PDL::Book
distribution if we could replace the images by
scripts to generate them, e.g., figure1.png.PL
My only caution would be the PGPLOT dependency required for making the
figure 'on the fly' as required.
Thinking about this more, do you mean that we'd put PDL::Book inside the
distribution with the *.png.PL scripts, but build the Book outside the
distribution with the images included?
The book itself will need to be independent of
the generation of the image data. That said, it
is a lot easier to avoid version skew if the
image data is generated by the actual example
code.
--Chris
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
