Slashdot Mirror
iPad 3 Confirmed To Have 2048x1536 Screen Resolution
bonch writes "After months of reporting on photos of iPad 3 screen parts, MacRumors finally obtained one for themselves and examined it under a microscope, confirming that the new screens will have twice the linear resolution of the iPad 2, with a whopping 2048x1536 pixel density. Hints of the new display's resolution were found in iBooks 2, which contains hi-DPI versions of its artwork. The iPad 3 is rumored to be launching in early March."
Apple will only multiply the resolution by two. Anything less compromises the quality of artwork on existing apps.
Unfortunately users at my company will still find a way to run them at 800x600
You laugh, but this is actually a serious reason why we don't have high-DPI displays on the mainstream desktop.
Not everyone has perfect 20/20 vision, or the same tolerance for small print. Many users already have problems reading text on existing displays when set to the default of 96 DPI. Unfortunately, the art of DPI scaling on mainstream OSes is still stuck in the dark ages. There are a LOT of poorly-written applications that assume 96 DPI and display badly broken output if anything else is set. Windows 7 is better than XP in its DPI scaling, but even so, it's far from perfect. Windows doesn't even support vector icons! The best you can do is to create a high-quality raster icon at 256x256 and hope it looks OK when downscaled.
This is why so many users run a LCD monitor at less than the recommended resolution. The slight blurriness is better for them than crystal-clear text too small to read, or various graphical nastiness from broken DPI scaling. Just today, in fact, I dealt with such a situation at work. One of our librarians said that some icons in the library management software were appearing all-black. I'd seen this issue before and knew it was due to the software not supporting 120 DPI, which this librarian had set for easier reading. I tried a few different things to see if I could get it to work – I set the "Disable display scaling" option in Compatibility properties, and also tried XP-style DPI scaling as well as the native Windows 7-style scaling. None of this worked. Ultimately, the only fix was to switch back to 96 DPI and run the monitor at a non-native resolution.
As long as this situation continues, monitor makers see no advantage in higher resolutions than 1080p, since so many users will just sacrifice that resolution for readability anyway.
I hated CRT monitors - they always got blurry when you ran them at super-high resolutions. Of course, I never bought the $2000 high end ones... (and having to run at 85Hz meant the monitor really only did 800x600).
The real reason cheap screens are 720p or 1080p is because the processing electronics is trivially cheap. It's basically the same as a regular HDTV. And that gives you a VGA and DVI/HDMI input "for free". To do 1920x1200 requires a different video processing chip for the monitor, which costs a lot more money because of the limited market (one reason why a 24" 1080p is available for under $200, while a 24" 1920x1200 is $500+).
Apple can do this because they're making these things by the millions, so they can buy in such huge quantities that high res stuff is cheap for them.
Are you kidding me? I'm voiding a couple mods I made but I just had to respond to this... utterly false statement. Have you ever done any iOS development at all? How about any Mac OS X development? Have you ever seen the Xcode developer tools? How about the Interface Builder component of Xcode? I've got a hunch that you haven't so I'm going to describe what it's like.
Interface builder is a WYSIWIG UI layout tool that generates XML files defining an application's interface to be loaded at runtime. Just about every app written for iOS has at least one of these interface files. The programmer uses Interface Building by dragging and dropping UI elements onto a sample device screen. You can resize and remask any element, as well as define new object templates with different appearance and behaviors. UIView objects, the base type of any interface element in the API, can be tweaked in an uncountable number of ways, as well as nested in other UIViews. The UI elements are linked to an Objective-C class that they are considered members of through a graphical relationship view.
Merely playing around with Interface Building for ten minutes will show you just how well iOS handles graphical scaling. Every piece of the UI kit is vector graphics and runtime rendering. Your uninformed conjecture has no basis in fact. Slashdot really needs a -1 wrong mod.