Quote:
Originally Posted by JSWolf
But, nook does use ADE code. And your sample was without a problem on my nook.
|
Which is why most of us on the boards usually stress actual testing on a bunch of different devices... and which is why I stress minimalism/simplicity in the code. Much less chance of things breaking because some devices decide to render code unexpectedly.
I really wish that there was a way where you could mass test code on a bunch of different ereaders. Most of us only own one, two, maybe three devices. I would say only the conversion companies have a mass of devices to test on.
I would think having one of each of the Kindles + each of the Nooks + perhaps a Kobo/Sony reader + an iOS/Android tablet + iOS/Android Phone would cover nearly all the bases.
Then just a few well-built test EPUBs, and feed it through all the devices. Take snapshots, take in-depth notes on comparisons. Sort of like what we had going at the PNG low-bit bug topic:
https://www.mobileread.com/forums/sho...d.php?t=222916
Quote:
Originally Posted by JSWolf
Maybe the problem was an old version of the system software in the store on the nooks.
|
Yes, that could be a possibility... I bet those display devices are just set up initially and rarely touched again. In the wild, I assume the situation would probably be even worse with unupdated devices.
Also, there is also the possibility of REGRESSIONS in firmware versions. Perhaps certain bugs have been fixed, but others may have been made worse. And then you have the devices which will just NEVER see an update ever again (like my original Nook).
Quote:
Originally Posted by JSWolf
As for iBooks, that's another issue. It has it's own quirks, flaws, bugs, and non-standardnesses. That and it is one nasty piece of work.
|
iBooks.. ugh. Let's not talk about that!
Quote:
Originally Posted by AuthorGreg
Well, after Tex reworked my CSS and HTML, my book finally displayed the same side-loaded as it did on the in-store Nooks. Liz Castro and Paul Salvette couldn't help me, but Tex did.
|
That is one of the reasons why I disliked a lot of the code in Liz Castro's book + site... iBooks specific code/workarounds, and just causes (in my opinion) tons of unmaintainable bloat.
Perhaps it is good if you are in the InDesign + iBooks only crowd.