×

First time here?

You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting!

Last week or so the PivotViewer control was released, which is from the Microsoft LiveLabs team.  It’s a Silverlight control that enables you to visualize data information in a DeepZoom type experience.  Be sure to check out the PivotViewer learning section for some initial information if you haven’t seen any demonstrations.

I received an email a few days back hoping for a more quick “how to” on using this control.  After all, it is a control for Silverlight and requires some implementation.  Honestly, I hadn’t even used it myself until I got that note.  I thought I’d jot down my notes in creating and consuming the simplest form of data and display using PivotViewer.  I say “simple” because you can get much more complex, but I wanted to simply show the quick steps.

Understand first that Pivot collections are a combinations of imagery and metadata that describe that imagery.  If you’ve ever seen the Hard Rock Memorabilia site that was done in early Silverlight days, this is the similar concept.

Step 1 – Get PivotViewer

The first thing you need to do is get the bits.  I’m going to assume you already have Visual Studio 2010 and Silverlight 4 Tools installed.  You can get the PivotViewer SDK at the PivotViewer learning section of the Silverlight community site.  Once you run the installer, the SDK will be installed to %ProgramFiles%\Microsoft SDKs\Silverlight\v4.0\PivotViewer\<RELEASE>.  There is a sample folder with source for an implementation as well if you want to look at it, but it has custom actions and things that you may not need.  My steps below are the “PivotViewer 101” steps to get a simple collection.  The sample provides more sample code to do other things with PivotViewer.

Step 2 – Get Pivot collection building tools

In order to use the control, you must have a Pivot collection source.  This is a specific data format in XML that the PivotViewer (and Pivot full client) use to understand the data.  The XML schema is documented here: PivotViewer Collection XML Schema.  As you can see it is fairly simple.  You could certainly build this by hand, but why would you when there are a few tools to help you!

There are 3 primary methods to create collection sources the way I see it: command-line, code library, and Excel.  The first two are most likely what any dynamic collection source will want to use.  These would be code-based approaches to looking at various types of data sources, appending metadata, and creating dynamically created collection sources or JIT-created ones as well.

The latter, using Excel, is the simplest.  The LiveLabs team created an Excel add-in to create the collection data using a familiar interface without having to really wrestle with the collection schema.  Once installed you have a new tab in Excel:

Excel PivotViewer collection tool

When you click the New Collection button on this tab, you’ll get a simple spreadsheet to start building your collection source.

Step 3 – Begin to build your collection data

For my sample, I’m going to use Bing’s wallpaper images from their last “Bing’s Best” Windows 7 themes.  Having my Excel sheet opened and already clicking on the New Collection function, I can now use the Import Images function to do this in bulk.  Now I don’t have to do this.  In fact, I can do one-by-one using the Choose Image function and select individual items.

I then wanted to provide a category column to enable my user to filter based on categories.  I used the Insert Column feature and gave it the title of Category.  These columns translate to Facets and if you see the schema definition diagram you will see that those visually translate to filters in the control.

Building collection data

Add your data until you are satisfied that you have all your data and metadata represented in this spreadsheet.  I only added one column but you could add more.  I am now complete and can choose to Publish my collection.

The result of the Publish function is that it will produce a file (CXML) and a folder of your DeepZoom-sliced images.  Remember this location of your data.

Step 4 – Build a Silverlight application implementing PivotViewer

Assuming you have the SDK installed, start a new Silverlight project in Visual Studio.  After that here were my simple steps:

Add reference to System.Windows.Pivot – add a reference to this assembly as this is where the PivotViewer control resides.

In my MainPage.xaml I then add an XMLNS declaration for the namespace and implement the control:

   1: <UserControl x:Class="SilverlightApplication164.MainPage"
   2:     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
   3:     xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
   4:     xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
   5:     xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
   6:              xmlns:pivot="clr-namespace:System.Windows.Pivot;assembly=System.Windows.Pivot"
   7:     mc:Ignorable="d"
   8:     d:DesignHeight="300" d:DesignWidth="400">
   9:  
  10:     <Grid x:Name="LayoutRoot" Background="White">
  11:         <pivot:PivotViewer x:Name="MainPivotViewer" />
  12:     </Grid>
  13: </UserControl>

That’s it for my simple scenario on the UI front.  I’m taking the approach that my app *is* the entire PivotViewer experience.

The next thing I wanted to do was make my simple viewer dynamic.  I wanted this same XAP to be used for any collection.  In my MainPage.xaml.cs code in the Loaded event I use the PivotViewer API and call the LoadCollection function:

   1: public MainPage()
   2: {
   3:     InitializeComponent();
   4:     Loaded += new RoutedEventHandler(MainPage_Loaded);
   5: }
   6:  
   7: void MainPage_Loaded(object sender, RoutedEventArgs e)
   8: {
   9:     string collection = App.Current.Host.InitParams["collection"].ToString();
  10:  
  11:     MainPivotViewer.LoadCollection(collection, string.Empty);
  12: }

You’ll notice that I’m getting a value from Silverlight’s InitParams model.  This enables me to send in the URL of the collection dynamically in my HTML hosting page:

   1: <object data="data:application/x-silverlight-2," type="application/x-silverlight-2" width="100%" height="100%">
   2:   <param name="source" value="ClientBin/SilverlightApplication164.xap"/>
   3:   <param name="onError" value="onSilverlightError" />
   4:   <param name="background" value="white" />
   5:   <param name="minRuntimeVersion" value="4.0.50424.0" />
   6:   <param name="autoUpgrade" value="true" />
   7:   <param name="initParams" value="collection=URL_TO_CXML" />
   8:   <a href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50424.0" style="text-decoration:none">
   9:        <img src="http://go.microsoft.com/fwlink/?LinkId=161376" alt="Get Microsoft Silverlight" style="border-style:none"/>
  10:   </a>
  11: </object>

So I can re-use this XAP in many places and just change the initParams value in the <object> tag.  I build the XAP and now I can place it anywhere.

Step 5- Publish the result

The final step is to publish everything.  Remember the CXML file and the folder of images?  They need to reside somewhere.  Here are two critical things to note:

  • If they (collection CXML file and images) are not residing in the same location as the XAP implementing the PivotViewer control, it must have cross-domain policies (clientaccesspolicy.xml) in place persuant to the rules of Silverlight and cross-domain.  Otherwise it won’t work.  PivotViewer makes network requests and this policy is required by Silverlight in cross-domain situations.
  • You may need to add a MIME type mapping on your server in order to serve the CXML file.  I did (on Windows 2003).  I simply added a MIME type mapping for .cxml and gave it the content type of text/xml and it worked.

Once I have all that published, I can deploy my HTML page hosting the XAP and pointing to my collection source.  As an example, here is my final result for this: Bing’s Best Pivot Collection.  Notice how the Category column now shows as a filter source on the left.  Had I made more columns, there would be more filter options.  I also could have made more metadata and populated the HREF attribute of the data to actually link to something.

The cool thing as well is that any collection that works with the Pivot schema works.  You can find some samples at the GetPivot Developer site:

Using the project the way I created it, I can just input these URLs in my initParams to change the collection I want it to view.  I was also able to use the Microsoft Organization Pivot Collection that LiveSide created directly in this without modification as well: MSFT Organization Pivot in Silverlight.

Summary

After spending a few minutes with the control, the simplest display scenario is very simple.  In fact, creating the collection source I think will be the most challenging…to determine what is the appropriate metadata that you need and want to display to your users to interact with in your application.

You can download my sample project here: PivotViewerSimpleSample.zip

Hope this helps!


This work is licensed under a Creative Commons Attribution By license.



DISCLAIMER:

The opinions/content expressed on this blog are provided "ASIS" with no warranties and are my own personal opinions/content (unless otherwise noted) and do not represent my employer's view in any way.