Search

A few months ago, I described a proof-of-concept project and learning exercise I'd worked on to implement some of the basics of the HTML 5 <canvas> specification using Silverlight as the underlying platform: HTML 5 <canvas> announcement, fix for other cultures. As I explain in the introductory post, I didn't set out to come up with the most efficient, most complete implementation - just to get some familiarity with the <canvas> specification and see what it would be like to implement it with Silverlight.

Probably the most requested feature for Silverlight 3 was being able to print or export the contents of a control so that we can save it and then print it. While there is no Print class of some sort directly available in Silverlight 3 either, we can print, using some small workaround. And that workaround goes by the name of the WriteableBitmap.

Note: This article is submitted by Antoni Dol for Silverlight Contest: Write and Win.Thanks a lot, Antoni! Hello All, Please drop a comment if you like it.

This Silverlight 2 development kick start helps you get over initial hurdles and clears the path for faster results.

Coming from projects in which WPF design experience was established, the step to developing in Silverlight 2 was not an easy one. Even though I anticipated getting disappointed and even annoyed by times, there were several gotchas that baffled me. Some of those can still be found in the current Beta 2 release, but others are resolved to a degree that makes for a workable Silverlight 2 environment.

This article is compatible with the latest version of Silverlight.

In response to Joe’s comment on the Canvas article about how the Canvas control deals with the Measure/Arrange process when it is laid out by a parent Panel:

It seems that during Measure/Arrange process the child Canvas will take zero width and height provided these properties are not set, even if it contains some controls. Here is a little example:

XAML:

We don’t see the Blue background of the inner Canvas because its size is zero.

This article is compatible with the latest version of Silverlight.

Introduction

Layout controls are Silverlight controls which act as containers of other controls. Their main purpose is the positioning and arranging of their child controls. There are several layout controls: Canvas, StackPanel and Grid and TabPanel.

See also:
Canvas Article
StackPanel Article
Grid Article

Overview

All layout controls derive from the basic abstract class Panel.

There are also four more descendants of the Panel Class: DataGridCellsPresenter, DataGridColumnHeadersPresenter, DataGridDetailsPresenter, DataGridRowsPresenter. Their purpose is the positioning of elements in a DataGrid template. They are not standalone controls.

Layout controls inherit the Children collection of type UIElementCollection. Since all elements in this collection are UIElement objects and the Panel itself derives from UIElement layout controls can be nested in one another without limitation.

The following example demonstrates the nesting:

Note: to understand this example you should be familiar with all layout controls: Canvas, StackPanel and Grid

We want to have the following meaningless result (I don’t like giving real world examples, I just want to show you how nesting of layout controls works.):

This article is compatible with the latest version of Silverlight.

Introduction

The Canvas is the simplest layout control used as a container for other Silverlight controls. The inner controls are positioned absolutely towards its left and top sides.

See also:
Silverlight Layout controls
Grid Article
StackPanel Article

Overview

The following example demonstrates the use of the Canvas:

We want to have a rectangle positioned 100 pixels from the left side and 50 pixels from the top side:

The child controls of the Canvas are positioned absolutely towards its left and top sides by their “Canvas.Left” and “Canvas.Top” attached properties.

Here is the XAML code: