Linked by Thom Holwerda on Tue 23rd Oct 2012 19:12 UTC
Thread beginning with comment 539965
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: resolution variability
by Torbjorn Vik Lunde on Thu 25th Oct 2012 11:51
in reply to "RE[3]: resolution variability"
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.




Member since:
2005-11-29
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.