Quote:
Originally Posted by Jellby
Really? Isn't it just that you expect a better quality for a high-resolution screen, and what you get is in fact about the same as a low-resolution one?
There are two cases for low-resolution images:
Images shown at their native resolution: They can look OK in low-resolution devices, but then they'll be damn small in high-resolution devices, with unreadable text if there's any.
Images scaled to some specific size: I don't see why they should look different in high-res or low-res devices. There may be small differences due to the scaling algorithm and the factors being different. If it's optimized for low-res, such that the scaling is 1:1, the quality may be somewhat degraded in high-res (aliasing etc.). If a case like this is unreadable in a high-res device, being OK in a low-res one, there's something seriously broken in the scaling algorithm.
On the other hand, high-resolution images have their own problems: large memory usage, overflow in low-res screens at native resolution, worse degradation when being scaled down.
|
I expect images I can see properly. I've seen many books that have maps where the maps are just too small on an 800x600 eInk screen and if you talk H2O and Voyage, it's going to be even worse.
When books are made these days, high resolution screens (like the HD, H2O, & Voyage) need to be taken into account. If you plan on doing full screen images, then you need to find out what size works so the images look good enough. Maybe 1200 line images. Maybe 1000 line images. I have not tested what image resolution works well on an H2O for full screen.
As for high resolution images having overflow issues on low-res screens, code for it. Code for a percentage of the screen and not a resolution. That way you'll get the images not overflow on low-res screens. The thing is, we have now 3 or 4 different screen resolutions and you cannot code for them using pixel sizing. You have to use screen percentages and you have to test on a these different screens to make sure you get it correct.