On 1/22/2012 3:57 PM, Matthew Kenworthy wrote:
I forgot to point out that =ff is just what is
needed to put page breaks at the start of each
chapter...
Ah! Good to know :)
I'm confused. Yes, the plan was to have a PDL::Book
distribution, which, by definition, would include the
PDL::Book.
I thought the ultimate idea was to put PDL::Book into the PDL-2.4.10
tarball, but the discussion about the sizes of the included images nixed
that idea. YOu can revive the diea by having PDL::Book only have text and
image generating scripts. I think that your point is to keep PDL::Book a
separate distribution entirely, which is where our confusion comes in.
OK. There seems to be an enormous amount of
interest in "putting" the PDL Book into the
PDL distribution.
While it _seems_ simple to just add it into
the current "kitchen sink" PDL has, the reality
is that if PDL were split into a core distribution
and a number of other, separate, distributions
corresponding to the external dependencies, we
would be *much* better off:
(1) The core would already be 100% ported since
it is mostly the external libraries and programs
that are difficult to get working consistently
across all platforms.
For example, a win32 PDL still takes
significant guru expertise to do. I *still*
can't do it. Although, if I took the time,
I could follow Rob's instructions and build
it eventually...
We work around that through Rob's generosity
to build and make available up-to-date PPD
versions of PDL CPAN releases, including the
latest developers release.
(2) Code improvement in PDL modules could happen
faster without having to wait for the entire
PDL distribution. By releasing frequent git
snapshots as developers releases, I've been
able to reduce some of the impact of this.
However, the developers releases are even
farther from 1-click installs then the CPAN
official releases.
(3) The full on, kitchen sink version of PDL
could still be bundled up and distributed
as a single distribution rather than the
possibly dicey use of cpan or cpanm to
build all the dependencies correctly.
(4) For similar reasons, having the PDL-Book-0.0.1
distribution works better: more frequent or
needed updates can be made as required, issues
of format generation and image generation will
continue to be worked out, a book isn't the
same thing as on-line help or documentation
(although they could be viewed with the same
utilities),...
Cheers,
Chris
And, I should add, at this point, this is a Good Idea.
The issue of generating the figures occurred to
me when I saw that the full size image looked
fine but that the scaled html image had lines
that were too thin and hard to see. It would
be better to have a separate NxN for HTML and
800x800 for PDF output.
Hmm, I think that good displayable single source images are possible with
HardLW=>5 and HardCH=>2 for illustrations. But that's something for the
release after this upcoming one!
Matt
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1416 / Virus Database: 2109/4759 - Release Date: 01/22/12
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
