Posted Nov 1, 2012 9:33 UTC (Thu) by Cato (subscriber, #7643)
Parent article: Quotes of the week
High resolution laptop screens are great as long as those with less than perfect eyesight can globally control all font sizes through a central DPI or "percentage enlargement" feature. Windows and Linux (X11's DPI) have this.
Unfortunately Mac OS X doesn't have this at all, so I'm reduced to application by application font size changes and custom plugins, on a Macbook Air 13" (1440x900). The result is that websites look terrible in Chrome for Mac on my laptop, due to Apple's insistence that resizing DPI globally is bad because it makes button images look worse. Oh the irony...
Posted Nov 1, 2012 10:55 UTC (Thu) by epa (subscriber, #39769)
[Link]
With the new Apple laptops they just apply a 2x scaling factor globally, which means that button images resize without getting ugly. On the 15-inch model the GPU then scales *down* by 0.75 to fit the display. A neat trick, but it wouldn't be necessary if the software were able to change the dpi setting properly.
Even if you have perfect eyesight, you don't want to view a 300ppi display with glyphs designed for 100ppi. My vision (after surgery) is better than average and my monitor is only 200ppi, but it still looks unreasonably tiny if you don't increase the font size.
Quotes of the week
Posted Nov 1, 2012 20:56 UTC (Thu) by bjencks (subscriber, #80303)
[Link]
The other problem that Windows and Linux have, but Apple doesn't, is that the DPI control is *global*. I have a nice 150ppi laptop screen, and things look great if I set the scaling appropriately on it. I also plug it into a nice big 96ppi monitor, and things look great on it if I set scaling back to "normal". But then things are tiny on the laptop display sitting right next to it.
Apple avoids this by only ever doing 2-to-1 scaling, and doing it on a per-display basis.
I've seen a few people argue against true resolution-independence on the basis that the current mechanism does something vaguely sensible on the monitor vs. TV use case where naive resolution-independence wouldn't. There seem to be two different variables that get conflated a lot: the actual density of the display, and the desired physical font size, which depends on the user's viewing distance, eyesight, personal preference, and even the PPI (I can read smaller fonts on higher density displays).
There's also the issue of how non-text UI elements should be scaled. For instance, widget borders would probably look pretty terrible at non-integer thicknesses. On the other hand, on a 300+ PPI display, single pixel borders start to be pretty hard to see.