I went through a period a few months ago trying to minimise the number of readers I have and settled on 2 for most frequest usage:
* Weasel Reader for books - fast and supports free fonts and VFS. * Plucker - for almost everything else.
I found that Plucker just wasn't suitable for book reading where the need is to be able to load a book fast, read comfortably, and scroll through pages fast if I want to move back or forward dozens of pages at a time.
With Plucker, the process is start App, Synchronise Documents, Select Document, Load Document. The document load time can be very long for large doucments, and page flipping speed is slower than a dedicated document reader. Also seeing each page render from top of page to bottom as you page flip is not (imho) a comfortable book reading experience.
With Weasel (and other book readers), page flipping speed is much faster, and the whole page appears when you move to the next page i.e. you don't see the page being rendered.
Also, you start the book reader app and immediately the last page you were looking at is visible. Yes, I know this can be the case with Plucker but only if you exit without passing through the library. If you have your hard keys mapped to Plucker functions then the only way directly out of a Plucker doucment is by tapping the Home icon on the silkscreen.
This is not a criticism of Plucker which I think is the greatest program on earth and bronze statues of the developers should be erected!
The questions of this post are:
Is it reasonable to expect Plucker to perform as a book reader?
Is it a future goal (of the developers et al) for Plucker to perform as a book reader and meet the useability standards of a book reader?
As a Plucker user, do you use a separate book reader (and if so, which one)?
Cheers, Stephen
_______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
