micke> 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
micke> You did read the INSTALL document, didn't you?
Yes, to get it installed; I'm not complaining about that. (I stopped
reading after "You set up your environment and install the viewer
application by running 'install-plucker'" which is all I needed to
know to install it.)
Now, I've read further in the INSTALL but there is nothing there on
usage (i.e. how to download a single webpage and load it into my
Visor).
What is there however, is a statement: "(for more info see README
files", which I then followed which then said: "For more information,
see the FAQ".
Why are there many levels of indirection? (INSTALL says look at the
README, README says look at the FAQ)
I would have found it much less frustrating if the README said:
"Please see the man-page for plucker-build in docs/plucker-build.1
for details on using plucker".
Also, what does plucker-dump do? There is no reference to
plucker-dump in any document in the root directory nor docs/
nor docs/Plucker_Doc/ (I just did a "grep plucker-dump *").
>> * --dbname should default to the contents of the
>> <title></title> tag of the document being downloaded.
micke> Well, I think the current solution makes more sense,
micke> i.e. default to the filename. Titles can be quite long and
micke> you would only get the first 26 chars.
I was looking for some mechanism that would automatically select a
default name for me rather than having to specify it; i.e. if
--dbname is not specified, then it would default to the contents of
<title></title>?
Are you concerned that 26 chars will not be unique enough to identify
the document?
micke> Use sitescooper (http://www.sitescooper.org) and you will
micke> get that indication. The viewer doesn't know whether a
micke> link is internal or external when it renders the text (and
micke> that is definitely nothing it should keep track of)
OK, I will look at that.
>> * Why do the bottom 2 lines of the previous page appear at the
>> top of the next page when scrolling?
micke> You need some context from the previous page. The exact
micke> amount could be changed, though.
OK, I would be satisfied with a config option.
micke> One idea I have is to replace these "Click here for
micke> next/previous part" with a new function code (this would
micke> also make it possible to translate this message for the
micke> different versions of the viewer) and together with
micke> records that contains references to the next/previous
micke> document for each record in the database it might be
micke> possible to "connect" the different parts of the document
micke> into one document.
I look forward to this.
micke> However, this is not at the top of my priority list.
:-(
Thank you for taking the time to respond.
