利用WPF和Silverlight进行MVVM高效应用开发

5星 · 超过95%的资源需积分: 16 111 浏览量更新于2024-07-26 收藏 4.17MB PDF 举报

"Apress.Pro.WPF.and.Silverlight.MVVM.Dec.2010.pdf" 本书《Pro WPF and Silverlight MVVM》由Gary McLean Hall撰写，专注于使用WPF（Windows Presentation Foundation）和Silverlight平台进行高效、可测试且可维护的应用程序开发，特别是通过Model-View-ViewModel（MVVM）设计模式来实现这一目标。MVVM是一种软件架构模式，广泛应用于UI开发，尤其是在.NET框架中的WPF和Silverlight项目中。在WPF和Silverlight开发中，MVVM模式扮演着核心角色。这个模式将应用程序分为三个主要组件：模型（Model）、视图（View）和视图模型（ViewModel）。模型负责处理业务逻辑和数据管理，视图是用户界面的呈现，而视图模型作为两者之间的桥梁，封装了视图与模型之间的交互逻辑，使代码更加解耦和易于测试。书中详细介绍了如何利用MVVM模式实现以下关键点： 1. **分离关注点**：MVVM帮助开发者明确职责，模型关注数据和业务规则，视图关注用户界面，视图模型处理两者间的交互，使得代码结构清晰。 2. **可测试性**：通过视图模型的独立性，可以编写单元测试来验证业务逻辑，而无需实际运行用户界面。 3. **数据绑定**：WPF和Silverlight强大的数据绑定特性在MVVM中得到充分利用，允许视图和视图模型之间自动同步，减少了手动更新界面的需求。 4. **命令与事件处理**：MVVM模式鼓励使用命令（如ICommand接口）来处理用户操作，使得视图模型能响应视图的事件，而无需直接操作视图元素。 5. **依赖注入**：为了提高代码的灵活性和可扩展性，书中可能涵盖如何使用依赖注入容器将依赖关系注入到视图模型中，以实现更好的组件复用和解耦。 6. **设计工具支持**：由于MVVM模式的流行，许多设计工具如Visual Studio和 Blend支持MVVM，提供更好的设计时体验和代码生成功能。 7. **实时通信与通讯机制**：可能会讲解如何利用消息总线（如MVVMLight的EventAggregator或 Prism的EventBroker）实现视图模型之间的通信，以及如何利用数据服务和异步操作来处理后台任务。 8. **最佳实践和模式**：书中的内容可能包括MVVM模式的常见最佳实践，如使用行为（Behaviors）扩展视图的功能，以及如何在大型项目中组织和管理视图模型。《Pro WPF and Silverlight MVVM》旨在帮助开发者充分利用MVVM模式的优势，构建健壮、可维护且高效的WPF和Silverlight应用。通过深入学习这本书，读者可以掌握MVVM的核心概念和技术，从而提升其在UI开发领域的专业技能。

■ CONTENTS

xiv

CHAPTER 1 ■ OVERVIEW OF WPF AND SILVERLIGHT

code wrapper around GDI+. Windows Forms, in particular, makes extensive use of this wrapper and this

is one of the key features that differentiates Windows Forms from WPF.

DirectX is an API built for graphically intensive applications, such as Computer Aided Design (CAD)

applications or video games. It provides an interface for rendering graphical scenes represented in three

dimensions onto a two-dimensional projection, such as your computer monitor. Along with OpenGL, it

is the industry standard for developing such applications, and the X in DirectX is itself the inspiration for

the X in XBox, so intrinsically linked are the two.

As managed .NET code can’t use unmanaged APIs directly, WPF uses a wrapper around DirectX as

an intermediary. MIL Core provides a low-level interface to the DirectX API, and WPF builds on top of

this to perform all of its graphical rendering. There are two consequences that arise from all of this: WPF

applications are graphically superior to Windows Forms applications; and WPF applications have a

higher minimum hardware—and, in fact, software—requirement than Windows Forms applications.

Graphically superior means that 3D is supported, cutting-edge graphical rendering techniques can be

employed, and any hardware acceleration present in the machine that is running the application will be

leveraged. The price paid for this is that WPF applications will run only on a minimum of Windows XP

Service Pack 2 because this is, in turn, the minimum requirement for .NET Framework 3.0. Similarly, if

you produce an application that makes use of advanced 3D rendering techniques, such as pixel shaders

and the like, you will require that your end users have sufficient hardware to run such an application. If

you must target operating systems such as Windows 98 or 2000, you may wish to use Windows Forms

instead.

Media

WPF has native support not only for displaying images but also for the playback of audio and video

multimedia.

As well as supporting established images formats—such as bitmap (BMP), Joint Photographics

Expert Group (JPEG), Graphics Interchange Format (GIF), and Portable Network Graphics (PNG) —

there is also an extensibility model for adding support for new image formats as they occur. This is built

on a new API that eliminates some of the limitations of GDI and GDI+, like high fidelity image support.

The System.Windows.Media.Imaging namespace contains much of the functionality for working with

images in WPF, while the System.Windows.Controls.Image class is the WPF control used for displaying an

image. The Image class’s Source property is used to set the location of the image file to display, as shown

in the example in Listing 1–1.

Listing 1–1. Displaying an Image Using the WPF Image Control

WPF supports the Windows Media Video (WMV), Moving Picture Experts Group (MPEG), and Audio

Video Interleave (AVI) file formats.

However, as the media component for WPF has Windows Media Player running behind the scenes,

WPF can use any other codecs that the Media Player has installed. For the playback of audio and video

files, the System.Windows.Controls.MediaElement control is used, again specifying a Source location of

the file to use, as in Listing 1–2.

Listing 1–2. Playback of a Multimedia File Using the MediaElement Control

CHAPTER 1 ■ OVERVIEW OF WPF AND SILVERLIGHT

Layout

While there are controls such as Image and MediaElement available to enable the creation of rich, modern

user interfaces, controls that provide general layout are no less important. WPF’s layout system contains

a number of controls that allow the user interface designer to arrange content in distinct ways.

To lay out controls, the layout system must calculate a variety of measurements in order to position

them before they are drawn. This is a recursive process because some controls can contain any number

of child controls, and this nesting can be very deep in some user interfaces. It is clear that arranging a

sufficiently complex layout may be an intensive process.

All controls possess a bounding box that invisibly demarcates its borders, and this can be tweaked

on a per-control basis using the Margin property, which is inherited by all FrameworkElement subclasses.

(See Listing 1–3.)

Listing 1–3. Using the Margin Property to Increase the Size of a Control’s Bounding Box

In a similar vein, the internal space within a control can be altered using the Padding property,

which is part of the Control class. (See Listing 1–4.)

Listing 1–4. Using the Padding Property to Alter the Internal Padding of a Control

Aside from altering layout-related properties on individual controls, there are controls dedicated to

the placement of their children. These controls inherit from the System.Windows.Controls.Panel class

and each has its own method of laying out the UIElements that form its Children.

As an example, the Canvas control allows its children to be positioned absolutely, using coordinates

that are relative to the Canvas’s area. The StackPanel, on the other hand, will position its children serially,

either vertically or horizontally.

Styling and Templating

WPF user interfaces often look more compelling than their Windows Forms counterparts. This is due, in

no small part, to the styling and templating system within WPF. Styles allow you to define a common

look and feel for multiple elements in a user interface. Templates, which come in different flavors,

facilitate more powerful changes to the underlying structure of controls.

Styles contain lists of property names and associated values, which allow you to change the

appearance of any controls that use the style. Listing 1–5 shows a button that is using an associated style.

Listing 1–5. Using Styling to Change the Appearance of Controls

<Setter.Value>

</Setter.Value>

</Setter>

</Style>

剩余272页未读，继续阅读

RuthlessAFei

粉丝: 1
资源: 4

利用WPF和Silverlight进行MVVM高效应用开发

Pro WPF and Silverlight MVVM Effective Application Development with 无水印pdf

Pro WPF and Silverlight MVVM-English

【英文版】Apress.Pro.WPF.and.Silverlight.MVVM.pdf

Apress.-.Pro.WPF.and.Silverlight.MVVM.2010

Apress.Foundations.of.WPF.Nov.2006.pdf

[android.开发书籍].Apress.Pro.Android.Media.Dec.2010.pdf

[Apress.J2EE系列].Apress.Pro.JSP.2.4th.Edition.Dec.2005

Apress.Pro.SQL.Server.2005.Assemblies.Dec.2005.pdf

Apress.Pro.JSP.2.4th.Edition.Dec.2005.pdf

Apress.Pro.SQL.Server.2005.Integration.Services.Dec.2007.pdf

最新资源