1. Building Silverlight Applications Jason Lee Ethos Technologies

3. Silverlight & XNA

4. Silverlight on Windows Phone 7

5. Development Tools

6. XAML

7. Play Time

8. DataBinding

9. MVVM

12. Comfort with XAML, event-driven application development

13. Vector Graphic

14. Rapid creation of a Rich Internet Application-style UI

15. Built-in controls

16. Embed video as part of screen

17. When to choose XNA

18. High-performance game

19. 3D

20. Familiar with Direct3D or even OpenGL

21. Or… both

23. Applications hosted on client device, not in browser.

24. Most features are Included :

25. Implicit Styles

26. DataBinding Enhancements

27. Icommand Support

28. Some are NOT Included :

29. Printing, MouseWheel

30. Right-Click

31. Drag and Drop

32. Phone Specific Additions

33. Gestures / Touch

34. Tasks (Phone Call, SMS, Email, Camera, etc.)

36. Great tool for coding, debugging, publishing

37. Only C# is supported for phone development

38. Can do some simple layout design

39. Expression Blend

40. Great tool for design

41. Has some overlap with Visual Studio

42. Principles

44. Extensible Application Markup Language.

45. Describing UI in the form of XML.

46. Used in WPF and Silverlight UI composition.

47. Everything done in XAML, can be done in C#.

48. Features

49. XML structure is ideal for describing hierarchical, nested Visual Tree.

50. Much more easier than C# to define/declare UI Elements, Templates, Styles, DataBindings.

51. Principle

52. UI related work goes to XAML, controlling work goes to C#.

55. Get familiar with development tools and project structure

56. Get familiar with basic controls

58. Two themes : Dark & Light

59. A number of Accent Colors

60. Thus, try NOT use specific color and font, use predefined resources instead.

61. Careful with Sizing

62. Phone resolution may defer, that’s why we need Auto-Size.

63. Auto-Size is great, but costs performance.

64. Thus, try NOT use too much Auto-Size, especially for hierarchical structure.

65. Appropriate Keyboard

66. Phone is small, we can’t show everything.

67. Show optimum keyboard to make users happy.

69. DataBinding is glue that joins presentation code(View) with controlling logic code(ViewModel) at runtime.

70. Make it possible to loose couple presentation layer and logic layer.

71. DataBinding Modes

72. Three different binding modes: OneTime, OneWay, TwoWay

73. Fundamental APIs

74. INotifyPropertyChanged

77. Set TextBox.Text = OriginalValue

80. DataBinding Modes Person TextBox Person TextBox Person TextBox OneWay TwoWay OneTime FirstName Text FirstName Text FirstName Text INotifyPropertyChanged

82. Set DataContext property of any UI Element

83. If the UI Element is a container control, all its containing sub-UI Elements inherit the same data source.Grid Person DataContext=“{Binding Person}” Text=“{Binding FirstName}” TextBox1 FirstName StackPanel Text=“{Binding MidName}” TextBox2 MidName Text=“{Binding LastName}” TextBox3 LastName

85. Set ItemsSource property of listcontrol (parent control).

86. List control generates a number of child-elements, applying each child’s DataContext with corresponding data source.

87. The look of each child is defined by parent control’s ItemTemplate.ListBox People ItemsSource=“{Binding People}” Person 1 ListBoxItem Person 1 Person 2 ListBoxItem Person 2 Person 3 ListBoxItem Person 3

89. Binding between event and method

90. Command binding is done through ICommandinterface.

92. Model-View-ViewModel

93. An alternative approach for MVC design pattern

94. Specially suitable for WPF/Silverlight

95. Advantages

96. Separation of concern

97. Reusability

98. Testability

99. Approaches

100. View First, ViewModel First

101. Principle

102. Design pattern is just a guideline for most common cases, you don’t have to do everything by applying it.

105. Derives from PhoneApplicationPageclass

106. Has a Title property

107. Optionally contains and shows ApplicationBar

108. Navigation

109. Silverlight on Windows Phone uses a Page-based navigation model

110. Similar to web page navigation model

111. Pages are identified by a unique URI

112. Key APIs

113. NavigationService.Navigate(Uri source)

114. NavigationService.GoBack()

115. Virtual void OnNavigatedFrom(NavigationEventArgs e)

117. The built in hardware Back key is used to navigate back to previous page

118. No code required to navigate back