On Tue, 27 Mar 2001, luis fernandes wrote:
> * When I initially unpacked it and tried to use it I found it very
> difficult to do what I was trying to do-- basically I wanted to
> download a single webpage and load it into my Visor
You did read the INSTALL document, didn't you?
> * --dbname should default to the contents of the <title></title> tag
> of the document being downloaded.
Well, I think the current solution makes more sense, i.e. default to
the filename. Titles can be quite long and you would only get the
first 26 chars.
> * User-interface issue: I would like to suggest that links not
> downloaded (followed) should either not be rendered in plucker or
> should be rendered in another distinct manner that indicates to the
> user, before he clicks on it, that it will not be followed.
Use sitescooper (http://www.sitescooper.org) and you will get that
indication. The viewer doesn't know whether a link is internal or
external when it renders the text (and that is definitely nothing
it should keep track of)
> * Why do the bottom 2 lines of the previous page appear at the top of
> the next page when scrolling?
You need some context from the previous page. The exact amount
could be changed, though.
> * Would it be possible to seamlessly read a large document rather
> than ask the user to click "Click here for next part", etc.
Not without several changes and that you are prepared to wait the
time it takes to calculate the total height of all the parts.
One idea I have is to replace these "Click here for next/previous
part" with a new function code (this would also make it possible
to translate this message for the different versions of the viewer)
and together with records that contains references to the next/previous
document for each record in the database it might be possible to
"connect" the different parts of the document into one document.
However, this is not at the top of my priority list.
/Mike
