《WPF Succinctly》英版技术详解：轻松掌握国外大神经验

需积分: 10 85 浏览量更新于2024-07-18 收藏 1.99MB PDF 举报

《WPF Succinctly》是由Buddy James撰写的一本关于Windows Presentation Foundation (WPF)的开发电子书。这本书以其简洁明了的风格受到了国外开发者的高度评价，尤其是在处理英文版时，相比于翻译版本，它更原汁原味地传达了WPF的核心理念和技术细节。书中在扉页有Daniel Jebaraj的前言，强调了WPF在Windows应用程序开发中的重要地位，以及作者Buddy James的专业知识和对技术的深入理解。版权信息表明，这本书由Syncfusion Inc.于2013年出版，位于北卡罗来纳州Morrisville的Aerial Center Parkway办公地址。该电子书是免费下载的，但需要通过官方网站www.syncfusion.com完成注册才能获取。未经授权的其他来源分发或传播本书的行为被严格禁止，仅限个人和教育用途使用。作者和版权所有者申明对此书提供的所有信息不提供任何形式的保证，包括但不限于无责任声明，即不对因阅读此书产生的任何损失或损害承担责任。此外，"SYNCFUSION", "SUCCINCTLY", "DELIVER INNOVATION WITH EASE", "ESSENTIAL" 和 ".NET ESSENTIALS" 是Syncfusion公司的注册商标，体现了其在软件开发领域的创新和专业知识。这本书对于希望深入了解WPF框架的开发者来说是一份宝贵的资源，涵盖了WPF的基础概念、控件、布局管理、数据绑定、用户界面设计等方面的知识。由于其内容详实且注重实践，无论是初学者还是经验丰富的开发人员，都能从中获益匪浅。同时，由于是英文原版，对于提升英文阅读能力和专业术语理解也有助益。《WPF Succinctly》是每个想要在Windows应用开发中掌握WPF技术的开发者不可或缺的学习材料。

using System.Windows;

using System.Windows.Media;

namespace Chapter01

{

/// <summary>

/// Interaction logic for MainWindow.xaml.

/// </summary>

public partial class MainWindow : Window

{

public MainWindow()

{

InitializeComponent();

}

private void btnGetRenderingTier_Click(object sender, RoutedEventArgs e)

{

//Shift the value 16 bits to retrieve the rendering tier.

int currentRenderingTier = (RenderCapability.Tier >> 16);

switch (currentRenderingTier)

{

//DirectX version level less than 7.0.

case 0:

txtRenderingTier.Text =

string.Format("{0} No hardware

acceleration.",

currentRenderingTier.ToString());

break;

//DirectX version level greater than 7.0 but less than 9.0.

case 1:

txtRenderingTier.Text =

string.Format("{0} Partial hardware

acceleration.",

currentRenderingTier.ToString());

Chapter 2 Inside WPF

What is XAML?

At the heart of WPF is a new XML-style declarative markup language called Extensible

Application Markup Language, or XAML (pronounced “Zammel”). The nature of XAML allows

the user interface to be completely independent from the logic in the code behind. As such, it’s

incredibly easy to allow a graphics designer to work in a design tool such as Expression Blend

while a developer works to complete the business logic in Visual Studio. XAML is a vast and

powerful language. This separation of design and development is one of the driving reasons

that Microsoft created XAML and WPF.

XAML allows the instantiation of .NET objects via declarative markup. You can import

namespaces to dictate the elements available to your markup. For instance, you can create a

class in C# that models a customer and declare the customer class as an application-level

resource. Then you can access this resource via XAML from anywhere in your application.

In a classic WinForms application, you would design your user interface in Visual Studio and the

IDE would emit C# or VB.NET in a partial class that represented the layout of your code. Each

control, be it a button, text box, or otherwise, would have a corresponding line of code.

In WPF and XAML, you use the IDE of your choice to create XAML markup. This markup isn’t

translated into code. It’s serialized into a set of tags that are loaded on the fly to generate the UI

of your application.

Elements represent objects, and attributes represent the objects’ property values.

Here’s an example:

1 <Window x:Class="Chapter01.ControlsExample"

2 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

3 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

4 Title="ControlsExample" Height="300" Width="300">

5 <Grid>

7 </Grid>

8 </Window>

Elements as objects, attributes as properties

Line one is the definition of the Window object. Just like any other XML-based language,

elements can be nested within other elements. The x:Class attribute specifies the name of the

Window’s class. This is the class in which we will access the window programmatically from the

code behind. Line two specifies the xmlns attribute, which represents a URI namespace. The

URI looks like a web resource, though it’s not.

The http://schemas.microsoft.com/winfx/2006/xaml/presentation namespace URI defines all of

the standard WPF controls. The xmlns is equivalent to the using statement in C#. Microsoft

chose this naming scheme because by using a URI with the Microsoft domain, it’s unlikely that

any other developer will use the same URIs when defining namespaces. There are roughly

twelve different standard WPF assembly namespaces and all of them start with

System.Windows. By specifying the URI, the code will search each of the namespaces and

automatically resolve that the Window element maps to the System.Windows.Window class. It

will find the Grid resides in the System.Windows.Controls assembly namespace.

Since line 2 imports the namespace in which all of the WPF elements reside, we do not add a

suffix. Line 3 represents another default WPF namespace that contains many utility classes that

dictate how your XAML document is interpreted. We apply the x suffix to this namespace. Then

to access elements of this namespace, we will prefix the element with x:. For example,

<x:MyElement>.

The following explanation of the xmlns attribute is taken from the XAML Overview (WPF) page

provided on the Microsoft Developer Network documentation on WPF at

https://msdn.microsoft.com/en-us/library/ms752059(v=vs.110).aspx.

The xmlns attribute specifically indicates the default XAML namespace. Within the

default XAML namespace, object elements in the markup can be specified without a

prefix. For most WPF application scenarios, and for almost all of the examples given in

the WPF sections of the SDK, the default XAML namespace is mapped to the WPF

namespace http://schemas.microsoft.com/winfx/2006/xaml/presentation. The xmlns:x

attribute indicates an additional XAML namespace, which maps the XAML language

namespace http://schemas.microsoft.com/winfx/2006/xaml.

This usage of xmlns to define a scope for usage and mapping of a namespace is

consistent with the XML 1.0 specification. XAML namespace is different from XML

namespace only in that a XAML namespace also implies something about how the

namespace's elements are backed by types when it comes to type resolution and

parsing the XAML.

Note that the xmlns attributes are only strictly necessary on the root element of each

XAML file. The xmlns definitions will apply to all descendant elements of the root

element (this behavior is again consistent with the XML 1.0 specification for xmlns). The

xmlns attributes are also permitted on other elements underneath the root, and would

apply to any descendant elements of the defining element. However, frequent definition

or redefinition of XAML namespaces can result in a XAML markup style that is difficult to

read.

The WPF implementation of its XAML processor includes an infrastructure that has

awareness of the WPF core assemblies. The WPF core assemblies are known to

contain the types that support the WPF mappings to the default XAML namespace. This

is enabled through configuration that is part of your project build file and the WPF build

and project systems. Therefore, declaring the default XAML namespace as the default

xmlns is all that is necessary to reference XAML elements that come from WPF

assemblies.

剩余109页未读，继续阅读

sinat_33766526

粉丝: 0
资源: 5

《WPF Succinctly》英版技术详解：轻松掌握国外大神经验

Windows Presentation Foundation Development Cookbook epub

Pro WPF 4.5 in C# （Pro WPF系列第四版 英文书及其源代码）

WPF 电子书翻书效果，实际上展示的是图片的翻页效果

Wpf电子书阅读器

WPF学习电子书

WPF入门电子书

WPF编程宝典电子书与源码

WPF揭秘-PDF 电子书

WPF深入浅出电子书

WPF 4.5 unleashed 最新版电子书

最新资源

Pro WPF 4.5 in C# （Pro WPF系列第四版英文书及其源代码）