Please consider adding "jump" feature

[GoogleCodeExporter]

Sometimes books.app forgets my reading position. This is inconvenient for long 
books. I have to 
make hundreds of scrolls to get to the position where i was at. Jump feature 
could largely solve this 
problem. for example, I know I was at about 60% of the book, so I jump to 60% 
and then make a few 
scrolls to find the exact spot.

Or, I have a book that I already read half of it on PC. Now I want to quickly 
scroll to 50%.

So, please consider adding the feature that allows me to jump to a certain 
percentage.

Thanks!

Original issue reported on code.google.com by samsonsu...@gmail.com on 28 Aug 2007 at 8:04

[GoogleCodeExporter]

This is a very good idea.  I'll try to make it happen for 1.0.

Original comment by roosters...@gmail.com on 29 Aug 2007 at 2:39

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This is looking to be very difficult, unfortunately--there's no way that I can 
find to determine how large the 
Scroller view is, which means I can't get a percentage of the view, and 
likewise I can't tell where a percentage of 
the text would fall.  What I may do instead is add "superscroll" buttons, which 
would allow you to jump by, say, 
ten screenfulls.  Would this do?

Original comment by roosters...@gmail.com on 30 Aug 2007 at 2:45

[GoogleCodeExporter]

Is it possible to simply count the number of bytes in the text? Or is there any 
other method that counts the text, even roughly?

As bottom line, yes, I think ten-screenful jump will work.

Let's do some simple maths. Take a 500KB txt file as example (it's almost the 
largest single file size without freezing the app), it contains 250K chinese 
characters. Usually I have about 200 ~ 250 chinese character per screen, so the 
entire file is split into about 1000 pages. To scroll to 50% of the book, which 
is 
500 pages, I need to tap on "superscroll" 50 times. That should be OK.

Please make sure if I tap superscroll quickly one after the other, the 2nd tap 
doesn't cancel the previous scrolling. In current version, if I tap the bottom 
of 
screen too quickly, the 2nd tap cancels the first one. This made fast scrolling 
impossible.

Thanks!

Original comment by samsonsu...@gmail.com on 30 Aug 2007 at 6:40

[GoogleCodeExporter]

It's certainly possible to get the length of the text.  The problem is that the 
UITextView doesn't scroll by text, but 
by pixels, and there's no way (that I can find) to match pixels with text.  So 
even if I knew where 50% was in the 
text (trivial, of course) I don't know where it lies in the rendered view (or 
even how large the rendered view is).

There is one possible solution, but it's horribly ugly.  I'll keep you posted.

Original comment by roosters...@gmail.com on 30 Aug 2007 at 5:54

[GoogleCodeExporter]

Another aspect / tack you might want to try is take a look at how the iPhone's
contact list allows you to scroll - and see if perhaps that gives any clues?

I'm a coding idiot, and completely okay with that. :)

Original comment by ken...@gmail.com on 4 Sep 2007 at 5:59

[GoogleCodeExporter]

I just want to add my 2cents here. A super scrolling or chapter / search 
function is
all I am pining for in this app. Thanks so much for this. I am a big eBook 
reader and
am thankful to have this on my iphone.

Original comment by dentalch...@gmail.com on 14 Sep 2007 at 3:05

[GoogleCodeExporter]

Original comment by roosters...@gmail.com on 5 Oct 2007 at 6:59

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I just posted to the SVN a hideable slider which will allow you to scroll from 
the beginning to the end virtually 
instantly.  It will be in the next release.

Original comment by roosters...@gmail.com on 8 Oct 2007 at 1:55

• Changed state: Fixed