This time straight into the topic:
XAML: System.Window.Control for a control (but most controls are derived indirectly) (Button:buttonBase:ContentControl: base class) Xaml:sl each element corresponds to a SL class, However, these classes do not represent all Silverlight applications, where the visible elements are mostly inherited System.Windows.UIElement (defining common event mouseleave,mouseenter, etc.) System.Windows.FrameworkElement is the definition of width, height, margin and other aspects of the layout of the problem and control class is defined as other such as font rendering, font size, background rendering, such as a strong commonality of properties! XAML painting elements: Shape () painting common Three: Line,rectangle,ellipsegeometry (geometry) linegeomatry,rectanglegeometry,ellipsegeometry XAML layout element:<canvas> grid, Stackpanel,dockpanel,wrappanel XAML Property element: A property element for XAML is a string, and some int is a double, and so on, It's all Typeconvert. Xaml property Assignment: 1: Property Assignment <textblock text= "Properties" >2: Attribute element assignment: <textblock ><TextBlock.Text> attribute Element </textblock.text></textblock>3: Content element Assignment <TextBlock> content element </textblock>4: Collection Assignment < Textblock.foreground>
<LinearGradientBrush>
<LinearGradientBrush.GradientStops>
<GradientStopCollection>
<gradientstop offset= "0.0" color= "Black" ></GradientStop>
<gradientstop offset= "1.0" color= "white" ></GradientStop>
</GradientStopCollection>
</LinearGradientBrush.GradientStops>
</LinearGradientBrush>
</textblock.foreground>5: attached property: For all supporting additional elements that work, make use of the parent element, and then support additional elements that inherit the attributes of the parent element such as: margin, Canvas.Left and so on. Type conversions, and bindings as well as the MVVM pattern
SL Second Article--Foundation