Composite Applications with WPF and PRISM
•Download as PPT, PDF•
0 likes•770 views
The document discusses composite applications with WPF and PRISM. It covers topics like Microsoft Expression Blend 4, the MVVM pattern, what PRISM is, regions and views, modules, and how PRISM can be used with WCF and for communication between modules using notifications and behaviors.
![About ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
More Related Content
Similar to Composite Applications with WPF and PRISM
Similar to Composite Applications with WPF and PRISM (20)
More from Eyal Vardi
More from Eyal Vardi (20)
Composite Applications with WPF and PRISM
- 1. Composite Applications with WPF and PRISM Eyal Vardi CEO E4D Solutions LTD Microsoft MVP Visual C# blog: www.eVardi.com
- 4. SKETCH FLOW
- 6. PHOTOSHOP
- 7. POWERPOINT
- 8. Blend
- 11. Theme & Skin Cosmopolitan JetPack Windows7
- 14. MOCKUP
- 19. Transitions < VisualStateManager.VisualStateGroups > < VisualStateGroup x : Name ="CommonStates"> < VisualStateGroup.Transitions > < VisualTransition To ="MouseOver" GeneratedDuration ="0:0:0.5"/> </ VisualStateGroup.Transitions > < VisualState x : Name ="Normal"/> < VisualState x : Name ="MouseOver" /> < VisualState x : Name ="Pressed" /> < VisualState x : Name ="Disabled" /> </ VisualStateGroup > ... </ VisualStateManager.VisualStateGroups >
- 20. Visual State Manager In XAML
- 23. Weather Control
- 24. Triggers, Actions & Behaviors
- 25. Action Way < Button Content ="Click Me"> < Button.Triggers > < EventTrigger RoutedEvent ="Click"> < EventTrigger.Actions > < BeginStoryboard Storyboard ="{StaticResource sbSpin}"/> </ EventTrigger.Actions > </ EventTrigger > < MultiTrigger > < MultiTrigger.Conditions > < Condition Property ="IsMouseOver" Value ="True" /> < Condition Property ="Content" Value ="{x:Null}" /> </ MultiTrigger.Conditions > < Setter Property ="Background" Value ="Yellow" /> </ MultiTrigger > </ Button.Triggers > </ Button > < Button Content ="Click Me"> < i:Interaction.Triggers > < i:EventTrigger EventName ="Click"> < E4D:MyAction TargetName ="lbTrace" /> </ i:EventTrigger > </ i:Interaction.Triggers > </ Button > public class MyAction : TargetedTriggerAction<DependencyObject > { public MyAction () { ... } protected override void Invoke( object o) { ... } }
- 26. Action
- 28. Timer Trigger Sample public class TimerTrigger : TriggerBase<DependencyObject > { public TimeSpan Interval { get ; set ; } protected override void OnAttached() { timer = new DispatcherTimer(); timer.Interval = Interval; timer.Tick += OnTick; timer.Start(); } void OnTick(object sender, EventArgs e) { this.InvokeActions(null); } protected override void OnDetaching() { timer.Tick -= OnTick; timer = null; } DispatcherTimer timer; }
- 29. Custom Trigger
- 32. Behaviors
- 33. FULL MOCKUP
- 34. Prism 2010
- 36. UI Module Structure ( MVVM )
- 37. Prism Quick Start (David Hill)
- 38. Prism & WCF Request Response Communication UI Shell
- 39. Prism & Notification Communication UI Shell Notification
- 40. Prism & Behaviors Request Communication UI Shell Response Notification B
- 41. FINISH
Editor's Notes
- If user experience matters, design matters. If design matters, designers matter. If designers matter, we need to make designers first class citizens of the traditional software development process. Let’s talk about how Microsoft is unlocking Developer and Designer collaboration and is empowering them to create successful UX software applications. 1) Traditionally designers would “mockup” the graphic design for a software application. Then by any means possible designers would deliver this “looks” to the developer… they would use JPG images, PNGs, PSDs or even Powerpoint presentations to express the designer intention. Then the developer would receive this “static images” and would try to convert that into reality. If the designer created some “non standard” controls, the developer was forced to code in GDI+ or other complex technologies to create the control raising the time and budget to such level that it was simply better to take the decision of making the UI more “standard”. The developer trying to recreate the idea of the designer would deliver something like what is shown on the right side of the screen. As you can see it represents only a tiny bit of the original vision. 2) In order to enable the collaboration between developers and designers, Microsoft has created XAML. XAML is the format which integrates the development process and is the way for both developers and designers to access the functionalities of WPF. As you can see we have no middle man anymore. XAML is generated by the designer, XAML is consumed by the developer. Further more, the workflow is now two-way meaning that the development process can also start from the developer side who creates XAML and then delivers this XAML to the designer which can take it and style it or completely redesign its appearance. 3) As a brief sample this are the tools that enable this kind of process: On the designer side we have Expression and on the Developer side we have Visual Studio.