03-09-2015, 06:06 AM | #1 |
Annabelle Viau
Posts: 43
Karma: 16664
Join Date: Jan 2015
Location: Rishikesh, India
Device: iPad, Kobo, Windows 10 (ADE, Azardi), Android (Google Books, Bluefire)
|
Loading page per page option for iBooks?
Hi,
I’m making a fixed-layout with CSS3 animations and some javascript. I have some issues with it on iBooks; it crashes when the book is opened. Someone told me it is possible to load each page by itself, page per page, instead of loading all of the pages as soon as the book is opened. Any informations on that? I’ve been searching but couldn’t find anyting. Thanks! |
03-09-2015, 07:23 AM | #2 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
It is probably not the size that is the culprit. I suspect faulty coding. Does it validate? Try it without the javascript.
|
03-09-2015, 07:48 AM | #3 | |
Annabelle Viau
Posts: 43
Karma: 16664
Join Date: Jan 2015
Location: Rishikesh, India
Device: iPad, Kobo, Windows 10 (ADE, Azardi), Android (Google Books, Bluefire)
|
Quote:
Also, it does validate. This is what made us think that the issue doesn’t come from the code, but from something else. |
|
03-09-2015, 11:54 AM | #4 | |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
The iPad 2 also is different then newer iPads as it only has 512MB of ram where the newer iPads all have 1GB (Ipad Air 2 has 2GB). So this book could be too memory intensive for anything below an iPad 3. If you have an iPad Air 2, then maybe your book needs more then 1GB to load all at once. We won;t have any idea until you tell us what iPads are being used for testing. Oh and specifying multiple as your devices doesn't help at all when you ask questions like this. |
|
03-10-2015, 06:44 AM | #5 |
Annabelle Viau
Posts: 43
Karma: 16664
Join Date: Jan 2015
Location: Rishikesh, India
Device: iPad, Kobo, Windows 10 (ADE, Azardi), Android (Google Books, Bluefire)
|
Ok so actually the device with problems is an iPhone 6 with iBooks 4.1.1.
This morning, we were able to see 4 pages before it crashed, but it was very slow, lagging. We have other books of the same kind (with animations) and on the same iPhone, there’s no issue... By the way, I didn’t see the point of writing which devices I own considering our books have to work on as many devices as possible anyways... |
03-10-2015, 09:26 AM | #6 | |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
03-10-2015, 10:23 PM | #7 |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Are you using CSS animation on margins and/or position, by some chance? Moving large raster images?
|
03-10-2015, 11:48 PM | #8 |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Do you perhaps have an iPad Air 2 which has 2GB of system ram?
|
03-11-2015, 09:15 AM | #9 |
Annabelle Viau
Posts: 43
Karma: 16664
Join Date: Jan 2015
Location: Rishikesh, India
Device: iPad, Kobo, Windows 10 (ADE, Azardi), Android (Google Books, Bluefire)
|
I really don’t get it. I did many tests, and at some point the book always crash. Here’s what I tested:
And I don’t have an iPad air... |
03-12-2015, 01:01 PM | #10 |
Addict
Posts: 398
Karma: 96448
Join Date: Dec 2013
Device: iPad
|
Did you try to update your iPad and reinstall iBooks? if that doesn't work i'm afraid you'll have to post some code :/
|
03-13-2015, 01:25 AM | #11 | |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Quote:
Short of something like that, I'd be surprised if the problem were caused by a lack of RAM, particularly given that the device that is failing has at least as much RAM as the one that is working. With that said, if you want to try to experiment with RAM reduction, the iBooks rendering engine (WebKit) always has just a single HTML file in memory at any given point in time, discarding the previous one as it passes a page boundary. Of course, there's also a back/forward cache and various other caches, so that's not precisely true, but either way, the less you put in a given HTML file, the less should be in memory at any given moment, and those caches are thrown away if you run out of memory, so they shouldn't be a problem. I mean, I suppose it is possible that iBooks might be doing something silly like extracting the entire Zip archive in RAM, but I doubt it. A couple more questions: 1. Does it fail reliably when you advance to any particular page? Or away from any particular page? 2. Could you paste in the crash log file? (It might not be of any help, but then again, it might.) |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PDF -> AWZ3: no go-to page option | sepandee | Conversion | 4 | 01-31-2014 01:37 PM |
K3 - Is the 'Every 6th page refresh' option possible? | Frothy | Kindle Developer's Corner | 4 | 01-01-2013 09:05 PM |
Page Refresh Option | jpcapili | Amazon Kindle | 1 | 11-21-2011 02:54 PM |
Page Loading Issue | MorganM | Kobo Reader | 6 | 03-14-2011 09:20 AM |