However smart the distiller will be, it will not be smart enough to tell
always whether text is nicely readable. A site might have some nasty
colors which, while "readable", will look ugly and will bother one after a
while. (E.g., I think one will be bothered when trying to read a large
text in red.) The site designer then is at fault, but we're not trying to
assign fault: we are trying to make the user's task easier. Now, it is
true that we can have an option in the distiller to fix the colors. BUT
it may be that only after reading for a while that one notices that the
colors are annoying. Or it may be that one has plucked the site, taken
one's PDA along for a trip, and only when traveling one notices that deep
down in the pluck there is a portion that is very annoying or hard to read
or whatever. One can't go back to the distiller to fix this. (One can
set the bit depth to 1, but that's ugly, too.) Or it may be that one has
plucked a large site over a slow connection, did not activate caching (I
still haven't figured out how to use caching myself), and one doesn't want
to re-pluck.
The option takes up very little code and is useful.
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
