I guess I am stubborn... Oh, yeah!
What if we look at this hi-res iPad display from a different perspective:
What if you are Apple and want to differentiate yourself from the competition by delivering a tablet with a higher-res display than any of them -- but you want to do so in such a way that it isn't disruptive to the developers (recoding) or a resource hog (programmatically scaling) -- yet isn't prohibitively expensive or difficult to manufacturer.
Is there anything you can do?
I think there is!
I have outlined my thoughts in a post to an earlier thread.
I want to illustrate, here, how current iPad apps might benefit from a slightly higher-rez display with no developer changes or rescaling. (All images are scaled 60% to conform to AI standards).
Fig 1: The Safari app displayed on the iPad
Fig 2: The Safari app displayed on the iPad showing the popup kb
Now, let's say the new iPad has a 1280x960 rez on the same screen. We can display the old 1024x768 res app unaltered, unscaled surrounded by black pixels. The actual display would be smaller, but still big enough. Note: The kb is a system-provided component and the system could automatically rescale the system kbs to the full width of the screen (maintaining the same height)
Fig 3: The Safari app displayed on the 1280x960 iPad showing kb
Here is one place we could gain from the higher-res display -- we could position the1024x768 content area at the top of the display and the bottom of the display could be used as a notifications / task bar (or somesuch).
Fig 4: The content area repositioned to the top of the display -- and a new task bar / notifications area on the bottom
We can take this a step further and have the system popup the kb from the bottom of the display -- revealing even more content
Fig 5: The content area repositioned to the top of the display -- and the kb popup from the bottom revealing more content -- here the system has scaled the kb to the full width of the screen
Compare figs 2 and 5 and you will see that we can see almost twice the content with the kb showing. Without rewriting, recompiling or rescaling of any kind.
Certainly, Apple would rewrite the system apps -- I used Safari because it is familiar.
I suspect that most current iPad apps would work quite well using this concept.
Likely, video and game apps would automatically rescale with a simple compile to support both the old and new rezes.
So, with a 1.25 x increase in display resolution, Apple could move the ball forward at minimal cost -- and little inconvenience to developers and users.
The original post where I discuss this in more detail is at:http://forums.appleinsider.com/showt...11#post1789311