Linked by Thom Holwerda on Tue 23rd Oct 2012 19:12 UTC
Apple It's one of those days again: Apple held a product announcement today, announcing several new products. The most important of which was rumoured about for a long time now: a smaller iPad. It's called the iPad mini, and has the potential to become the best-selling iPad - and thus, the best selling tablet.
Thread beginning with comment 539824
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: resolution variability
by Torbjorn Vik Lunde on Wed 24th Oct 2012 06:04 UTC in reply to "RE: resolution variability"
Torbjorn Vik Lunde
Member since:

Unless you are talking about the technique of pixel doubling a display (or another multiplier that results in integers, not floats) I strongly disagree. When I resize vectors (typically in Photoshop) to a by a non-even multiplier such as 1.33 (used by Nexus 7) i often have to re-arrange and redraw a lot of my graphics. With 2X (Retina Apple stuff, some Android devices) I just resize and all of it looks sharp (I might still do some adjustment, but I need to do way less than with non-even numbers.)

Even if you export everything to vectors you still have to think about where on the pixel grid those vectors actually fall (this will affect how sharp things look).

Bjango have a excellent blog post on this subject if you want to know more:

Reply Parent Score: 2

RE[3]: resolution variability
by Nelson on Thu 25th Oct 2012 07:17 in reply to "RE[2]: resolution variability"
Nelson Member since:

The XAML stack handles all of this easily.

By default the layout is adaptive, though you can opt-in to a fixed layout with a styled letterbox (Often even showing relevant content).

The only place where scaling by non whole multipliers is a problem is when using bitmapped content, which is why Microsoft has guidelines to where possible provide images at specific scales.

Even then, you can control the quality of the scaling of Bitmaps in the event that you don't control the scales that they're presented at (Remote images or something).

On top of that, you can tell the Layout engine to round its measurements and not put you on a sub-pixel boundary (Which causes fuzziness even with vector drawing) using UseLayoutRounding.

There's very simple rules developers should follow on Windows 8 and they'll be fine scaling to higher resolutions and differing aspect ratios.

Reply Parent Score: 2

Torbjorn Vik Lunde Member since:

My comments about vectors applies to XAML as well. You still have to consider where things fall on the pixel grid.

Now it’s not impossible, we’ve been making complex adaptable layouts for browsers for some while now… it’s just way harder than dealing with a fixed surface such as the iPad or a piece of printed paper.

Reply Parent Score: 1