On Sun, Oct 07, 2001, Earl H. Merry wrote: Earl,
Thanks for the feedback. I will try to answer some of your questions/ranting (my "speciality" is the viewer, though:) > ;;maxwidth = 150 > ;;maxheight = 250 > ;;can't figure out what these do. . .I don't need em =) You *do* use them if you include images larger than 150x250. All keys in the default .pluckerrc file that has a value assigned to them show you the value that will be used by default unless you change it (and uncomment the key). I hope that explains why the image tools are used although they are not uncommented in your .pluckerrc file. > The documentation is outdated and confusing. I know, but until a technical writer volunteers to write a better User's Guide you will have to live with the current documentation. > Why does my djpeg convert jpegs so nicely even though it's commented > out in the rc!? Answered above. > The rc is confusing. What is confusing? Please provide more details or we can't really "fix" it. > Why all the different formats for command line switches? That's the way it is done in the Unix world, i.e. both a short and long name for each option. > The special plucker:URL syntax is confusing as hell. . . You don't have to use it ... use an absolute path instead, e.g. plucker-build -H http://somewhere.com -f /home/micke/Anywhere will create a Plucker document called Anywhere.pdb in my home dir. > Marketing-wise, The evil M-word ;-) > plucker needs to hone its language on just exactly what this app does, I thought that was quite obvious. It makes it possible to read, on your handheld, web pages and any document that can be converted to HTML or text. > how many pieces make up the app, As many as it takes... Today, it should be enough to install python, netpbm (or ImageMagick or PIL) and jpeg. It has been worse... > and how the heck you use it. If the manual is "unreadable" then you can read the source code, instead ;-) Seriously, it is not that easy for anyone involved in this project to write a good manual, since we are too "blind" to the problems a normal user runs into. Even more important is the fact that if we are not told about the problems then we can't do much about them. > Plucker could dominate the market for palm viewing of web content > if the parts could come together a little tighter. I'm not sure I want to "dominate the market". I don't know about the rest of the team members, but I spend way too much time on this as it is ;-) /Mike
