BUILD2011

Reach all your customer's devices with one beautiful XAML user interface

Download this episode

Download Video

Description

Windows runs on a broad array of devices and form factors. Get your app on all the devices your customers use by building a great user experience that adapts to different screen sizes, aspect ratios and pixel densities using XAML. Learn how your app can take advantage of new multi-tasking views and orientations and see how easy it is to build apps that look great on different screen sizes and on high pixel density screens.

Day:

3

Code:

APP-847T

Room:

Lassen

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • karl1406

      Very nice presentation.

      Karl

    • ianoakes

      At 15 minutes Tim talks about star sizing grids, he says that a column with a Width of 250* is 'defined as a minimum of 250 but takes up the rest of the available space'. As a WPF guy this statement got my attention because in WPF this would be incorrect.

      The following is an excerpt from the WPF documentation.

      In Extensible Application Markup Language (XAML), star values are expressed as * or 2*. In the first case, the row or column would receive one times the available space; in the second case, the row or column would receive two times the available space, and so on.

      So in Tim's example the column would receive 250 times the available space, but since he's set the other two columns to a fixed width of 250, it doesn't really make sense. In fact omitting the 250 and just leaving the * produces the same effect, a column that takes up all available space.

      Now I'm pretty sure this hasn't changed in Windows XAML either. Looking at XAML documentation star sizing still seems to work the same way as WPF, feel free to correct me if I'm wrong.

    • BSalita

      Presentation needs less powerpoint text and more images. The same content could be conveyed in half the time.

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.