> The Visor does not seem to accept 4-grayscale (2bpp) images, it only
> shows them in black-and-white (although I set colour depth to 2 in the
> Preferences) and stretched by a factor of 2 vertically (so I can only
> see the left half of the image).
I have a Visor Deluxe, and although the battery life on the Visor is
atroscious, it definately displays 2bpp greyscale properly. The "stretched"
image is a hint that you're probably using a --max{width|height} value
somewhere or an --alt{maxwidth|maxheight} value. I've never seen images
stretched on Plucker at all, unless I screwed up those two values.
As you probably figured out, PalmOS versions before 3.0 only
supported monochrome in APIs. Palm OS versions 3.0 through 3.3 somewhat
supported 2 bit gray. Palm OS 3.5 and above supports up to 8 bit for devices
that support it. Your Visor is running 3.1H, modified a bit for Handspring's
hardware.
That being said, let's go through a quick debug:
1. Are you running any hacks on your Visor? Any SysTrap() calls?
2. What version of Plucker?
What version of the parser?
What version of Python?
What version of netpbm2/PIL/ImageMagick?
3. What is the URL you're gathering, and what are the parameters
you're passing to it to gather it?
4. What OS on your host computer? Windows? Solaris? OS/2? Linux?
5. What does your ~/.pluckerrc look like? Are you overriding
parameters in ~/.pluckerrc by passing the parser arguments when
you run it?
With those answers, we can better diagnose what might be going on.
> I am certain that my Visor can display 4 grayscales, the Handspring
> "About" or "Info" windows display grayscales.
This may help:
http://www.palmos.com/dev/tech/hardware/compare.html
> I have tried various combinations of netpbm and ImageMagick and the
> --bpp option, but could not achieve a satisfying result.
You mean netpbm2, right? You don't see 'ppmtoTbmp' trying to run
anywhere, do you? Are your netpbm2 palm templates working? Are they in the
right place to be found by netpbm2? For example (in .pluckerrc)
palm1bit_graymap_file = /usr/lib/palmgray1.map
palm2bit_graymap_file = /usr/lib/palmgray2.map
palm4bit_graymap_file = /usr/lib/palmgray4.map
palm8bit_stdcolormap_file = /usr/lib/palmcolor8.map
palm16bit_stdcolormap_file = /usr/lib/palmcolor16.map
You'll only need the first two since your Visor will not support
more colors/levels of grey than that.
> The other problem is the handling of the maxdepth flag (-M or MAXDEPTH
> directive in HREFs). With a maxdepth of 1, it only seems to download the
> specified page but not to follow any links, but with maxdepth=2 it seems
> to craw an additional 2 levels down the "tree". I would want it to only
> follow one additional level, but I cannot seem to manage that. What am I
> missing here?
Currently, a maxdepth value of 1 will download the page referenced.
A maxdepth of 2 will download that page, and the pages of the links
referenced on it (I still disagree with this numbering, but.. not my call
right now). When you run the parser, and use --maxdepth=1 or --maxdepth=2,
there should only be a 1-page difference in the levels it gathers. It
shouldn't skip any levels, unless there are overriding parameters in either
the URL construct you pass to Plucker, or the ~/.pluckerrc file again. Try
using --maxdepth=2 on the commandline and see if that helps. I've never ever
used the -M at all, so I can't say that it works, but I know --maxdepth
definately does.
Hope that helps.
/d
