Windows 8 Metro应用开发：XAML与C#实战

4星 · 超过85%的资源需积分: 10 161 浏览量更新于2024-07-27 收藏 1.89MB PDF 举报

"《Metro Revealed：使用XAML和C#构建Windows 8应用》是Apress出版社出版的一本技术书籍，专注于介绍Windows 8 Metro风格应用的开发。作者是Adam Freeman，书中涵盖5个主要章节，分别涉及入门、数据绑定和页面、AppBars、Flyouts及导航、布局和磁贴以及应用生命周期和合同。" 这本书详细讲解了Windows 8 Metro应用的构建过程，使用XAML和C#这两种主要的编程语言。XAML（Extensible Application Markup Language）是一种用于描述用户界面的标记语言，常用于.NET框架下的WPF（Windows Presentation Foundation）和UWP（Universal Windows Platform）应用，提供了声明式编程模型，使开发者能够更直观地设计UI。在入门章节，作者会引导读者了解Windows 8开发环境的设置，包括安装Visual Studio IDE和必要的SDK，以及创建第一个Metro应用的基础步骤。开发者还将学习到如何使用XAML创建基本的UI元素，如按钮、文本框等，并理解如何通过C#代码与XAML进行交互。数据绑定和页面章节则深入探讨了如何在应用中管理和展示数据。数据绑定是将UI元素与数据源连接的关键技术，使得UI可以动态反映数据的变化。此外，页面管理是构建多页应用的重要部分，书中会解释如何在不同页面间导航，以及如何使用导航堆栈保持状态。 AppBars和Flyouts是Metro UI中的重要组件，提供了一种简洁的用户交互方式。AppBar通常位于屏幕边缘，提供常用的操作选项，而Flyouts则提供额外的信息或功能，不占据主屏幕空间。在这一章，读者将学习如何创建和自定义这些元素，以提供优秀的用户体验。布局和磁贴章节关注于UI的设计和响应式布局。Windows 8的磁贴设计是其特色之一，允许动态更新并展示通知。开发者将学习如何使用不同的布局容器（如Grid、StackPanel、WrapPanel等）来适应不同设备的屏幕尺寸，以及如何创建和管理动态磁贴。最后，应用生命周期和合同章节讨论了Windows 8应用如何启动、暂停、恢复和关闭，以及如何利用合同（如分享、搜索和设置合同）与其他应用进行交互。理解应用生命周期对于确保应用在各种状态下表现良好至关重要。《Metro Revealed》提供了全面的指导，帮助开发者掌握Windows 8平台上的应用开发，无论你是初学者还是有经验的程序员，都能从中受益，开发出符合现代用户界面标准的高效且引人入胜的应用程序。

CHAPTER 1 ■ GETTING STARTED

XAML may strike you as verbose and hard to read at ﬁrst, but you will soon get used to it. I ﬁnd that it is a

lot easier to work with XAML than using just C# code, although I admit it took me quite some time with XAML

before I decided that was the case.

Running and Debugging a Metro App

Now that we have a very simple Metro app, it is time to focus on how to run and debug a Metro app. Visual Studio

provides three ways to run a Metro app: on the local machine, on the simulator, or on a remote machine.

e problem with the local machine is that development PCs are rarely conﬁgured the way that user devices

are. Unless you are targeting your app at people with similar spec platforms, then testing on the local machine

doesn’t give you a representative view of how your application can behave.

Testing on a remote machine is the best approach, but only if you have a range of machines with dierent

capabilities to test with, which is difﬁcult at this point, given that so few Windows 8 machines are available

(although I have a small Dell laptop that runs the Consumer Preview of Windows 8 quite happily and lets me

debug touchscreen issues).

Tip ■ You need to download and install the Remote Tools for Visual Studio 11 Beta from http://preview.win-

dows.com

on each remote machine you want to test an app on.

e best compromise is the Visual Studio simulator, which provides faithful representation of the Metro

experience and lets you change the capabilities of the device you are simulating, including changing the screen

size, simulating touch events, and generating synthetic geolocation data. To select the simulator, locate the

button on the Visual Studio toolbar that currently says Local Machine, and click the small downward arrow just to

the right of it. Select Simulator from the pop-up menu, as shown in Figure 1-5.

Figure 1-5. Selecting the Visual Studio simulator to test Metro apps

Running a Metro App in the Simulator

To start the example app, click the toolbar button (which will now say Simulator), or select Start with Debug

from the Debug menu. Visual Studio will start the simulator and build and deploy the Metro app, as show in

Figure 1-6.

Chapter 2

Data, Binding, and Pages

In this chapter, I show you how to deﬁne and use the data that forms the core of a Metro application. To do this,

I will be loosely following the view model pattern, which allows me to cleanly separate the data from the parts of

the app that are responsible for displaying that data and handling user interactions.

You may already be familiar with view models from design patterns such as Model-View-Controller (MVC)

and Model-View-View Controller (MVVC). I am not going to get into the details of these patterns in this book.

ere is a lot of good information about MVC and MVVC available, starting with Wikipedia, which has some

balanced and insightful descriptions.

I ﬁnd the beneﬁts of using a view model to be enormous and well worth considering for all but the simplest

Metro projects, and I recommend you seriously consider following the same path. I am not a pattern zealot, and I

ﬁrmly believe in taking the parts of patterns and techniques that solve real problems and adapting them to work

in speciﬁc projects. To that end, you will ﬁnd that I take a pretty liberal view of how a view model should be used.

is chapter is focused on the behind-the-scenes plumbing in a Metro app, creating a foundation that I can

build to demonstrate dierent Metro features. I start slowly, deﬁning a simple view model, and demonstrate

dierent techniques for bringing the data from the view model into the application display using data binding.

I then show you how you can break down your application into multiple pages and bring those pages into

the main layout, changing which pages are used to reﬂect the state of your Metro app. Table 2-1 provides the

summary for this chapter.

Table 2-1. Chapter Summary

Problem Solution Listing

Create an observable class. Implement the InotifyPropertyChanged interface. 1

Create an observable collection. Use the ObservableCollection class. 2

Change the Page loaded when

a Metro app starts.

Change the type speciﬁed in the OnLaunched

method in App.xaml.cs.

Set the source for data binding values. Use the DataContext property. 4

Create reusable styles and templates. Create a resource dictionary. 5, 6

Bind UI controls to the view model. Use the Binding keyword. 7

Add another Page to the app layout. Add a Frame to the main layout and use the

Navigate method to specify the Page to display.

8, 10

Dynamically insert pages into the app layout. Use the Frame.Navigate method, optionally

passing a context object to the embedded Page.

CHAPTER 2 ■ DATA, BINDING, AND PAGES

Caution ■ You will need to uninstall the example Metro app from the previous chapter if you are following the

examples using the source code download from Apress.com. Right-click the MetroGrocer Start menu tile in the

simulator and select Uninstall. If you run an app that has already been installed from a different project path, Visual

Studio will report an error. You must uninstall as you move from one chapter to another.

Adding a View Model

At the heart of a good Metro app is a view model, the use of which lets me keep my application data separate

from the way it is presented to the user. View models are an essential foundation for creating apps that are easy to

enhance and maintain over time. It can be tempting to treat the data contained in a particular UI control as being

authoritative, but you will soon reach a point where ﬁguring out where your data is and how it should be updated

is unmanageable.

To begin, I have created a new folder in the Visual Studio project called Data and have created two new class

ﬁles. e ﬁrst deﬁnes the GroceryItem class, which represents a single item on the grocery list. You can see the

contents of GroceryItem.cs in Listing 2-1.

Listing 2-1. e GroceryItem Class

using System.ComponentModel;

namespace MetroGrocer.Data {

public class GroceryItem : INotifyPropertyChanged {

private string name, store;

private int quantity;

public string Name {

get { return name; }

set { name = value; NotifyPropertyChanged("Name"); }

}

public int Quantity {

get { return quantity; }

set { quantity = value; NotifyPropertyChanged("Quantity"); }

}

public string Store {

get { return store; }

set { store = value; NotifyPropertyChanged("Store"); }

}

public event PropertyChangedEventHandler PropertyChanged;

private void NotifyPropertyChanged(string propName) {

if (PropertyChanged != null) {

PropertyChanged(this, new PropertyChangedEventArgs(propName));

}

is class deﬁnes properties for the name and quantity of the item to be purchased and which store it should

be bought from. e only noteworthy aspect of this class is that it is observable. One of the nice features about

剩余97页未读，继续阅读

Salvini

粉丝: 0
资源: 23

Windows 8 Metro应用开发：XAML与C#实战

Metro Revealed: Building Windows 8 apps with XAML and C#

Apress.Metro Revealed Building Windows 8 Apps with XAML and C Sharp Jun 2012

[DevDiv翻译]Metro Revealed_ Building Windows 8 apps with XAML and C#_第三章 应用.pdf

What is the difference between “display: none” and “visibility: hidden”, when used as attributes to the HTML element.Verify your answer with your own examples.

aurix_hsm revealed_training_demo_1.0

stated preference和revealed preference有什么区别

近3年的Java参考文献

最新资源

[DevDiv翻译]Metro Revealed_ Building Windows 8 apps with XAML and C#_第三章应用.pdf