Docstoc

izcode.net - 06 - Sử dụng User Control thực thi Master-Detail Scenarios

Document Sample
izcode.net - 06 - Sử dụng User Control thực thi Master-Detail Scenarios Powered By Docstoc
					Phần 6: Sử dụng User Control thực thi Master/Detail
Scenarios
                                      Understanding User Controls

A fundamental design goal of Silverlight and WPF is to enable developers to be able to easily
encapsulate UI functionality into re-usable controls. Developers can implement new custom controls by
deriving a class from one of the existing Control classes (either a Control base class or from a control like
TextBox, Button, etc). Alternatively they can create re-usable User Controls - which make it easy to use a
XAML markup file to compose a control's UI, and which are easy to implement.

For our Digg application, we want to implement a master/details scenario where the application allows an
end-user to search on a topic, populate a list of stories related to that topic, and then enable them to
select a story to bring up details about it. For example, selecting the below story in the list:




would bring up this detailed view about the story:
We are going to implement this details view by building a "StoryDetailsView" UserControl that we'll
display when a story is selected from our ListBox.

Creating a StoryDetailsView User Control

We'll start by right-clicking on our DiggSample project node in Visual Studio and by selecting "Add New
Item". This will bring up a new item dialog. We'll select the UserControl item template and name the new
control we want to build "StoryDetailsView":
This will add a new UserControl with this name to our DiggSample project:




Building a Basic Modal Dialog Using a User Control

We are going to use our StoryDetailsView control to effectively display a dialog containing story details.
When our story details user control displays we are going to want to have it appear on top of the other
content on the page, and ensure that an end-user can't do other things with the page until they close the
details view.
There are a couple of different ways we could implement this modal dialog-like behavior. For this
particular scenario we are going to start by opening up the StoryDetailsView.xaml user control and adding
the below XAML content to it:




The first <Rectangle> control above is configured to stretch to take up all of the available space on the
screen. Its background fill color is a somewhat transparent gray (because its Opactity is .765 you can
see a little of what is behind it). The second <Border> control will then be layered on top of this
Rectangle control, and take up a fixed width on the screen. It has a blue background color, and contains
a Close button.

When visible, our StoryDetailsView user control will currently display a UI like below:
We can implement the "CloseBtn_Click" event handler method in the code-behind file of the user control.
When pressed, the close button event handler will set the Visibility of the UserControl to "Collapsed" -
which will cause it to disappear from the screen and return the user to the content below it:




Displaying our StoryDetailsView Control

An easy way to cause our StoryDetailsView user control to appear on the screen would be to simply add
it to the bottom of our Page.xaml file, and set its default visibility to Collapsed (which means it is not
visible when the application first loads):




We can then handle the "SelectionChanged" event from our ListBox control within the Page.xaml's code-
behind class:
When a user selects a particular story in the list, we can use the ListBox SelectionChanged event handler
to set the Visibility property of our ShowDetailsView user control to "Visible" :




This will cause our modal user control dialog to appear. When the user clicks its "Close" button, it will
disappear, and the user will be free to select another story and repeat the process.

Passing Story Data to our StoryDetailsView User Control

Ultimately we want our StoryDetailsView UserControl to display detailed information about the story that
the end-user selected from the stories ListBox.

Within our ListBox's "SelectionChanged" event handler (which is inside our page's code-behind class), we
can gain access to the DiggStory data object that corresponds to the selected ListBox row by accessing
the ListBox's "SelectedItem" property.

One approach we could use to pass this DiggStory object to our StoryDetailsView UserControl would be
to simply set the "DataContext" property on the User Control to the selected DiggStory data object
immediately before making the user control visible:
We could then write code within our UserControl to procedurally use the DataContext to display results.
Or alternatively we could use databinding expressions to bind against its values.

For example, we could update our StoryDetailsView XAML to display the Title of the selected story using
a databinding expression like below:




And now when a user clicks a story in the list:
Our ListBox event handler will handle the selection, set the DataContext of the UserControl to the
selected DiggStory object, and then make the user control visible:




Notice how the DiggStory title now appears in the user control because of the databinding expression we
added to it.
Finishing our User Control Layout

Our sample above demonstrates the basics of how we can put together a simple master/details dialog
workflow. We can complete the StoryDetailsView display by adding more controls and databinding
expressions to the User Control.




We could update the StoryDetailsView user control to look like above by updating its <Border> control to
have the following inner content:
No code changes are required after this. Because we are using databinding to "pull" the values from the
DataContext, we don't need to write any additional code.

				
DOCUMENT INFO
Shared By:
Stats:
views:26
posted:8/24/2010
language:Vietnamese
pages:10
Description: IzCode.Net - Ebooks Developer - Webdesign - Template - Source Script - PHP - C# - .Net - Sliverlight