Apple displays ... 133dpi?
If apple increased it's 20" display to 133dpi (like the new powerbooks), it would reach (and surpass) the 1080i minimum to be considered HD. It would also make the 23" display a lot less necessary, as the only reason they released it at all was because it had the pixel count to be considered HD.
Having HD across the line would make for a better marketing strategy, as well.
What do you guys think?
- Xidius
Having HD across the line would make for a better marketing strategy, as well.
What do you guys think?
- Xidius
Comments
- Xidius
Originally posted by drumsticks
I have asked this question many times in many different places (here including). What is it that laptop display densities are on the rise, but desktop ones remain roughly the same?
My money is on 133DPI+ displays next year, along with the anouncement of a resolution-independant ui being a main feature of the upcoming 10.5.
When 10.4 was coming out, they made reference to it, and said that as of 10.4 you would be able to specify the DPI your app was being built for, and would self-scale when the system for it was built. (The default res, iirc was 72dpi)
So.. We have a ui that can already scale (roughly though.. bitmaps ftl), which is also gpu-excellerated (quartz extreme).. Does anyone else smell the possibility of the first practical 3d gui on the horizon?
- Xidius
Originally posted by drumsticks
I have asked this question many times in many different places (here including). What is it that laptop display densities are on the rise, but desktop ones remain roughly the same?
There's a few factors at work here. First, viewing distances tend to be larger on desktop displays. Unless you're using a separate keyboard and mouse, you'll often be very close to a laptop's screen.
Second, if this is your only system, you'll want quite a bit of screen area to work from - especially if the system costs $2500. Having 1680x1050 gives you the equivalent space of Apple's 20" display, and that can mean using the laptop as your only system rather than needing a complementary box.
Lastly, I suspect that LCD costs are more sensitive on the desktop side. After all, on a laptop people are willing to pay to get extra workspace. They're less likely to do that on the desktop side.
http://www.hellas-sat.net/library/File30.pdf
Apple claimed that 100 dpi was the optimum resolution for any screens.
Laptops can reach 133, but you are looking them more closely than their big brothers counterparts.
Originally posted by Powerdoc
I ordered a 23 incher for my quad G5 and I visited the Apple's web pages related to the Apple LCD screens.
Apple claimed that 100 dpi was the optimum resolution for any screens.
Laptops can reach 133, but you are looking them more closely than their big brothers counterparts.
That's completely false! 100ppi is not optimal. Apple makes that claim only because their UI is not completely scalable at the moment. More is always better. Think printers...
Originally posted by drumsticks
That's completely false! 100ppi is not optimal. Apple makes that claim only because their UI is not completely scalable at the moment. More is always better. Think printers...
For printers may be, but for using software like Word, I doubt it is. Try to read a text with a police size 10 on a very high resolution ...
What you say is true, for pics, but not true for text.
Originally posted by Powerdoc
What you say is true, for pics, but not true for text.
It will be true for anything once Mac OS X becomes resolution independent.
Originally posted by PB
It will be true for anything once Mac OS X becomes resolution independent.
That's right, but it's not currently the case.
Originally posted by Powerdoc
That's right, but it's not currently the case.
Again true.
I am wondering however how long it will take before we see resolution-independence as a well established feature of OS X. If I am not mistaken, it is already there and disabled in Tiger, just to give developers a reason to work with it. I guess it will come with Leopard (isn't that 10.5?), since this one has to compete against Longhorn.
Originally posted by PB
Again true.
I am wondering however how long it will take before we see resolution-independence as a well established feature of OS X. If I am not mistaken, it is already there and disabled in Tiger, just to give developers a reason to work with it. I guess it will come with Leopard (isn't that 10.5?), since this one has to compete against Longhorn.
It will be a nice feature indeed. It will allow people with poor eyes to type write directly in the right size font.
Originally posted by NordicMan
So with 10.5 Leopard, there likely will be new Apple displays?
Originally posted by wmf
Once OS X becomes resolution-independent, the number of lines of text on the screen will be a function of the physical size, not the resolution. Thus switching to a smaller screen (23" -> 20") allows you to fit less text on the screen (but the text is sharper). I'd prefer the 23".
once os x becomes resolution-independent, i hope to be able to set ui size to my preference...
To my disappointment the resolution scaling is very buggy. I had hoped it would be much further along the development process.
Not even Apple's own applications work as of yet. The Finder goofs up badly with font sizes. Mail's buttons become useless. Safari kinda works, but tabs tend to be drawn on top of the address bar making entering a new web address difficult. And web pages with Java content completely screw up.
Interestingly Image Ready CS2 kind of works, but Photoshop doesn't at all. Microsoft Office is also not usable.
In a nutshell, we're miles away from that feature unfortunately. And as far as I am aware there is no way of using vector graphic icons either (ideally resolution independent PDFs). OS X is still stuck in multi-resolution raster images making all icons and buttons blurry when viewed in anything but the native resolution. On that department Longhorn seems much more advanced.
From all this my guess is that this feature will only be half-supported even in OSX 10.5 as Apple and developers need to do a lot of work to get this to a useful state. I presume it will not truly happen until OSX 10.5.5 or 10.6.
I'm not holding my breath.