Lesson 02 Introduction to XAML
Download as PPTX, PDF0 likes49 views
XAML is an XML-based markup language that allows developers to define user interfaces and objects in code that is more readable than raw code. It uses markup extensions like binding, static resource, and dynamic resource to connect properties between objects at runtime. XAML code is separated from programming logic and can be designed visually using tools like Expression Blend.
Lesson 02 Introduction to XAML
- 2. XAML stands for ExtensibleApplication Markup Language. Its a simple language based on XML
- 3. XAML code is short and clear to read Separation of designer code and logic Supported by powerful graphical design tools like Expression Blend
- 7. Markup extensions are dynamic placeholders for attribute values in XAML. They resolve the value of a property at runtime Built-in markup extensions
- 8. Binding ▪ To bind the values of two properties together. StaticResource ▪ One time lookup of a resource entry DynamicResource ▪ Auto updating lookup of a resource entry TemplateBinding ▪ To bind a property of a control template to a dependency property of the control x:Static ▪ Resolve the value of a static property. x:Null ▪ Return null
- 10. XAML <Button x:Name="btnButton" Grid.Row="1" Content="Click Me!" Click="Button_Click"/> Code btnButton.Click += Button_Click;
Editor's Notes
- #3: All you can do in XAML can also be done in code. XAML is just another way to create and initialize objects
- #6: Properties are normally written inline as known from XML <Button Content="OK" />. But what if we want to put a more complex object as content like an image that has properties itself or maybe a whole grid panel? To do that we can use the property element syntax. This allows us to extract the property as an own child element.
- #7: When you declare a BorderBrush, the word "Blue" is only a string. The implicit BrushConverter makes a System.Windows.Media.Brushes.Blue out of it. The same regards to the border thickness that is beeing converted implicit into a Thickness object. WPF includes a lot of type converters for built-in classes, but you can also write type converters for your own classses.
- #8: Example: Background="{StaticResource NormalBackgroundBrush}"
- #10: At the beginning of every XAML file you need to include two namespaces. The first is http://schemas.microsoft.com/winfx/2006/xaml/presentation. It is mapped to all wpf controls in System.Windows.Controls. The second is http://schemas.microsoft.com/winfx/2006/xaml it is mapped to System.Windows.Markup that defines the XAML keywords. The mapping between an XML namespace and a CLR namespace is done by the Xmlns attribute at assembly level. You can also directly include a CLR namespace in XAML by using the clr-namespace: prefix.