Ezequiel Jadib : Windows Presentation Foundation

New Samples in CompositeWPF (Prism) Contrib (2008-09-13)

ejadib — Sat, 13 Sep 2008 20:38:15 GMT

Four new samples has been added to the CompositeWPF Contrib community project:

Silverlight & Composite Application Guidance (Prism): Spike published

ejadib — Wed, 06 Aug 2008 19:10:29 GMT

Weeks ago we shipped the Composite Application Guidance for WPF and with the Prism team we started to spike around the migration of the Composite Application Library to Silverlight 2 Beta 2. The good news is that yesterday we published that spike. (A ’spike’ is a small and quickly developed sample application in order to mitigate some risks).

After downloading and decompressing the latest change set of the source control, you will find a new folder named spikes that contains the Composite Application Library migrated to Silverlight. As you may imagine, there were many challenges that we had to address in order to make it “work” (Rob Eisenberg wrote two articles describing differences between WPF and Silverlight that you might want to check: There’s some darkness in your silver light and Silverlight Problems That Affect Me).

Note: The migration is not complete, we used the spike to have a perspective of the challenges.

Read the full article

CompositeWPF (Prism) Contrib Latest Additions (2008-07-26)

ejadib — Sat, 26 Jul 2008 20:40:15 GMT

These are the latest extensions added to the CompositeWPF Contrib community project:

Read the full article.

Use the OutlookBar in your CompositeWPF (Prism) Applications

ejadib — Tue, 22 Jul 2008 00:22:47 GMT

Two years ago, together with Matias Woloski we wrote the Outlook Bar for the Composite Application Block (CAB). I can say that it was a popular workspace, with more than 19,000 downloads!. Now that we shipped CompositeWPF (Prism), some people at the CompositeWPF community started asking for the OutlookBar for CompositeWPF, so Julian Dominguez, Matias Woloski and me decided to spend some time and create the Composite WPF version.

Read the full article.

CompositeWPF (Prism) Contrib Latest Additions

ejadib — Sat, 12 Jul 2008 18:07:38 GMT

A week ago we shipped the Composite Application Guidance for WPF and many people (including me) started to contribute in the CompositeWPF Contrib community project and to play with the guidance.

Let’s explore the latest additions added to the CompositeWPF Contrib project.

Read the full article.

Composite Application Guidance for WPF Visual Studio Templates

ejadib — Thu, 03 Jul 2008 16:56:06 GMT

As you may know, in the June 2008 release of the Composite Application Guidance for WPF we are not shipping a guidance package. So, I created two Visual Studio Templates to help you to start with the creation of a solution using the Composite Application Guidance for WPF.

Composite Application Guidance for WPF (Prism) June 2008 Released

ejadib — Thu, 03 Jul 2008 16:00:54 GMT

I’m proud to announce that we have just released the Composite Application Guidance for WPF. I want to thank to the Composite WPF Team. It was really great being part of this release.

Let’s see what this release is about.

Composite Application Guidance for WPF (Prism) Release Candidate Published

ejadib — Mon, 30 Jun 2008 12:58:55 GMT

Last Friday, we published the release candidate version of the Composite Application Guidance for WPF (formerly known as Prism). In this release you will find a Reference Implementation, a Hands on-Lab, several spikes we did, some QuickStarts, the Composite Application Library and documentation.

Prism: New drop published

ejadib — Tue, 03 Jun 2008 18:39:42 GMT

A new drop of Prism has been published last Thursday. Among other things, in this drop we refactored the Bootstrapper by extracting common functionality into a base class named UnityPrismBootstrapper located in the Prism.UnityContainerAdapter project.

Prism How-To: Provide metadata to a view that was placed into a region

ejadib — Thu, 24 Apr 2008 17:02:17 GMT

If you downloaded our fourth drop probably you may have noticed that we have removed the IMetadataInfo and IMetadataInfoProvider classes. (See Julian's post for more info about this change).

In the Prism Forum some people are asking how to provide metadata to the view now that the IMetadataInfo class has been removed, so in this post I will explain how to do it.

Imagine that you have a TabRegion named MainRegion in your Shell and you want to add a view to it.

 <TabControl Name="Tab" Prism:RegionManager.Region="MainRegion">

After you do this

regionManagerService.GetRegion("MainRegion").Add(new View())

you will see something like the following picture

Looks good, but... we don't have a header, so let's see how to do it

Create a HeaderModel class

namespace PrismTabHeader
{
    using System.Windows;

    public class HeaderModel : DependencyObject
    {
        public static readonly DependencyProperty HeaderInfoProperty =
            DependencyProperty.Register("HeaderInfo", typeof(string), typeof(HeaderModel));

        public string HeaderInfo
        {
            get { return (string)GetValue(HeaderInfoProperty); }
            set { SetValue(HeaderInfoProperty, value); }
        }
    }
}

This class contains a HeaderInfo dependency property.

Update the view by adding the Model property.

public HeaderModel Model
{
    get { return DataContext as HeaderModel; }
    set { DataContext = value; }
}

Create a new style named HeaderStyle in the Shell.

<Window.Resources>
  <Style TargetType="{x:Type TabItem}" x:Key="HeaderStyle">
     <Setter Property="Header" Value="{Binding RelativeSource={RelativeSource Self}, Path=Content.DataContext.HeaderInfo}" />
  </Style>
</Window.Resources>
This style is going to be applied to TabItem elements and is saying that the value of the property Header is going to binded to Content.DataContext.HeaderInfo where Content is the view.

Note: You can also expose a HeaderInfo property in the view and change the binding path to Content.HeaderInfo.

Replace the TabControl definition of your Shell with the following code

<TabControl Name="Tab" Prism:RegionManager.Region="MainRegion" ItemContainerStyle="{StaticResource HeaderStyle}" />
As you may see we are setting the ItemContainerStyle dependency property to affect the appearance of the elements that contain the data items. In this case, the style is going to be applied to all TabItem elements within the scope the style is defined in.

Set the Model to the view before adding it to the region

View view = new View();

view.Model = new HeaderModel() { HeaderInfo = "My Header" };
 
region.Add(view);

If you run now the application you will see the header.

Hope this helps.

Crossposting from here