Hello friends, I am wanting to use Plucker for eBooks that I will make available to a certain audience and want to make them available for a free reader. However, the 32kB restriction is a significant problem for me, because it chops the text in the middle of a sentence.
Worse yet, is the fact that if you click on the link to move to the next "page", then click on the link at the top of that page which takes you back to the previous page, you are returned to the top of the previous page, not the end of the page where you just came from, making it very awkward to read across the page break which falls in the middle of a sentence. What I wish is that Plucker could somehow manage this internal memory segment in a manner which was hidden from the user--in such a way that the user never realized that the page limit was used internally. Since there does not appear to be an archive of the list messages, I do not have access to where this issue might have been discussed before. Is there someone who can clue me into why Plucker is stuck with this hard page boundary (and I don't mean the hardware constraints of Palm hardware, since other eBook readers don't force a user to work around hard boundaries)? Would it not be possible to use two 16kB buffers so that both sides of a page break could be resident and blended together to allow a smooth transition between them? Part of the reason for my question is that I am considering creating a reader for a custom requirement and think that Plucker is a good starting point. -- Darren Hiebert <[EMAIL PROTECTED]> http://darren.hiebert.com
