Feature request on page turning

[GoogleCodeExporter]

I am a great eBook reader. I've read on palms and some phones. No doubt
when I got my iPhone I downloaded this right away!

The big surprise is that it doesn't quite work as the other eBooks readers
I've come to use:

1. The last line of text is shown even if incomplete. This is a no-no. On a
book I have a number of lines that is not fractional.
2. When going to the next page, it shows the last line displayed. I want a
continuous flow of reading, and this is just annoying at every page turn.

In short, what would be great is: Hide the last incomplete line and when
going to the next page do not repeat a line.

As it is it looks more like a text file viewer than a real ebook viewer.

That said, thanks a bunch for all the effort. The rest is cool for me.

Original issue reported on code.google.com by pier...@gmail.com on 10 Feb 2008 at 8:32

[GoogleCodeExporter]

Ah yes, one more thing: The screen should never start with an incomplete line 
either
(of course, if the user scrolls then let it be). When going to the next page, I
expect to see exactly that: A page. There is no data from the last page in 
there, no
data cropped.

Original comment by pier...@gmail.com on 11 Feb 2008 at 12:24

[GoogleCodeExporter]

Just to add my two bits, I think this issue might revolve around the fact that
iphonebooks doesn't have the notion of a page. It just renders the whole text 
file
and allow the user to scroll within the rendered pane. Going to the next page 
is just
a "hack" that scrolls down 400 lines or so. There is no notion of page number 
as well
for this very reason.

Fixing this issue will probably solve the huge file issues (where loading a 5MB 
text
file can be problematic). iphonebooks should just render the current page 
(maybe the
next one as well for performace purposes). The first time a book is opened it 
should
computes the number of pages and maybe index those pages so that going to an
arbitrary page if fast.

Of course, the page definition will change whenever the user chooses to go
widescreen, display/hide the bars or change font.

I am willing to help get this done if given a chance. I don't even know the 
language
this thing is written on ! Can we get in touch? pieroxy at gmail.

Original comment by pier...@gmail.com on 12 Feb 2008 at 9:33

[GoogleCodeExporter]

Original comment by pendorbo...@gmail.com on 17 Feb 2008 at 6:15

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Another issue of not having page numbers is that you have no way of knowing 
where you
are in a book (precisely that is). If I am reading a 900 pages book and am 
somewhere
inside, then I need to reformat my iphone for some reason, I don't have a real
information to store in order to be able to resume my book where I left it (I 
mean
not easily).

Original comment by pier...@gmail.com on 21 Feb 2008 at 4:36

[GoogleCodeExporter]

Original comment by pendorbo...@gmail.com on 23 Feb 2008 at 7:05

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by pendorbo...@gmail.com on 11 Jun 2008 at 3:31

• Changed state: WontFix