At least in terms of native applications I've seen literally no differences; maybe Metro handles it better but Metro on the desktop is, well, Metro on the desktop.
PS - I know it is now called "Modern UI" but that name sucks.
At least in terms of native applications I've seen literally no differences; maybe Metro handles it better but Metro on the desktop is, well, Metro on the desktop.
PS - I know it is now called "Modern UI" but that name sucks.
A lot more detail about the mbp and 8: http://blogs.msdn.com/b/tonyschr/archive/2012/08/29/windows-...
eg here is one blog post from 2006, which in turn refers to guide written in 2001 http://blogs.msdn.com/b/greg_schechter/archive/2006/08/07/69...
iirc there was some similar blog-post series about high dpi stuff when windows 7 was released, but I couldn't find it now with google.
Once you get into a proportional mindset, the hardest problems tend to be related to text and images. One trick I learned for the latter was using vector art as much as possible and converting SVG images to XAML (care of XamlExport[1]). Then scaling no longer becomes an issue. For raster art, I would hope Metro has something similar to iOS's retina graphic substitution magic. Silverlight 4 didn't which was a bit of a drag.
Text was always a little trickier but when dealing with full screen apps I would usually just have some code that changed the text size based on the delta between the new and old window size.
That said, you mentioned that Metro will do image substitution a la iOS. Thats fantastic and something I sorely missed during my Silverlight dev days.
I can't answer the to specifics of how rendering is different between 7 and 8, but the frameworks released with 8 have or are moving towards vector and resolution-independent rendering.
http://www.zdnet.com/microsoft-design-language-the-newest-of...