XPlorerBar: A WPF Windows XP Style Explorer Bar Control

• Download demo project - 526.36 KB
• Download source - 760.67 KB

Table of Contents

• Introduction
• What's New in v1.1
• What the Demo Application Looks Like
• Design Goals
• Functional Requirements
• Using the Code
• Identifying XPlorerBar Elements
• Accessing XPlorerBar Elements
• Adding an XPlorerBar to your Application
• Registering and Applying a Custom Theme
• Using XPlorerSection Template Parts
• Building an XPlorerBar with Bindings
• Themes
• Project Structure
• Documentation
• Tools
• Feedback
• Future Work
• History

Introduction

XPlorerBar is a WPF implementation of the left side pane that was introduced in Windows XP's explorer. It provides a visually attractive and versatile way to present a grouped list of options while making effective use of screen space; common usage scenarios would include providing access to multiple areas of an application or presenting multiple pages of information.

Although there are many versions of this control for Windows Forms, its implementation for WPF is rather rare and, most of the time, paying. So, as I was looking for a good idea to deepen my learning WPF, I decided to write one myself as a learning exercise.

To see the XPlorerBar in action, download the demo executable and give it a try!

What's New in v1.1

• Added the Blend theme to the built-in themes of the library.
• Added a completely new class for theme management which allows to apply themes to any FrameworkElement object (for more information, see Registering and Applying a Custom Theme).
• Updated the XPlorerBar class so that it is bindable (for more information see Building an XPlorerBar with Bindings).

What the Demo Application Looks Like

The demo application, which can be downloaded at the top of this article, allows:

• the modification of several parameters of the XPlorerBar located on the left [A],
• to click on the header of a section to expand/collapse it [B],
• to click on any item in a section [C].

Design Goals

Ease of use - The naming of components, methods, properties and events is consistent with the framework naming rules.

Fully customizable - All the elements (brushes, controls, geometries, animations duration, ...) are fully customizable: merge with the XPlorerBar.Generic.xaml dictionary and redefine the styles and/or templates of the items you want to customize.

Accurate look & feel - Colors and sizes of all the elements match exactly (thanks to the GIMP [^]) with the real Windows themes: 7 built-in themes are included for Vista, XP and NT.

Fully documented - As I would like this project to be helpful to the devs, the source code is highly commented and the library's API is provided as an MSDN style documentation file.

Functional Requirements

• Req 01 - An XPlorerBar hosts a vertical stack of sections, called XPlorerSection.
• Req 02 - A vertical scrollbar is automatically added when all the sections cannot be fully displayed (remark : the horizontal scrollbar is never displayed).
• Req 03 - An XPlorerSection contains a fixed header and an expandable/collapsible content.
• Req 04 - An XPlorerSection header can host a large icon and its associated text. If the text cannot be fully displayed, it is cropped to the header width and an ellipsis is added to indicate that cropping has occurred.
• Req 05 - XPlorerSection contents can be expanded or collapsed by clicking on their headers.
• Req 06 - Each XPlorerSection uses animations when its content is being expanded (fade in and slide down) or collapsed (fade out and slide up). Remark: animation durations have to be customizable by the user.
• Req 07 - Even if an XPlorerSection can host any sort of content, an XPlorerItem component is provided to easily display a text with its small icon, add hot tracking and a 'Click' event to the command.
• Req 08 - If an XPlorerItem cannot be fully displayed, its text is wrapped to the header width and ends on the next line.
• Req 09 - An XPlorerSection can be designated as 'Primary' to be displayed differently than 'normal' sections.
• Req 10 - Most of the XPlorerBar elements (brushes, controls, geometries, ...) have to be easily accessible to the user.
• Req 11 - The user can apply any (built-in or custom) theme to the XPlorerBar.
• Req 12 - If no specific theme is applied to the XPlorerBar, it automatically obtains its colors from the active Windows theme.

Using the Code

The XPlorerBar control and its associated elements are located in the ZonaTools.XPlorerBar namespace. Make sure you add a reference to the compiled library ZonaTools.XPlorerBar.dll before using it.

Identifying XPlorerBar Elements

The image below identifies key parts of XPlorerBar control:

1. XPlorerSection[Primary]Header[Hover]ForegroundBrush
2. XPlorerSection[Primary]HeaderBackgroundBrush
3. Key parts of an XPlorerSection button are:
   • XPlorerSection[Primary]HeaderButtonBackgroundBrush
   • XPlorerSection[Primary]HeaderButton[Hover]ForegroundBrush
   • XPlorerSection[Primary]HeaderButtonBorderBrush
   • XPlorerSectionHeaderExpandArrows
   • XPlorerSectionHeaderCollapseArrows
4. XPlorerBarBackgroundBrush
5. XPlorerSection[Primary]Content[Hover]ForegroundBrush
6. XPlorerSection[Primary]ContentBackgroundBrush
7. XPlorerSection[Primary]ContentBorderBrush

Remark: the words inside of square brackets are optional:

• 'Primary' is set when the XPlorerSection is set as 'Primary' (e.g. XPlorerSectionPrimaryContentBorderBrush).
• 'Hover' is set when the mouse is over an element (e.g. XPlorerSectionHeaderHoverForegroundBrush).

Accessing XPlorerBar Elements

All the above elements can be reused in your own templates.

The sample code below shows how to assign the background brush of the active XPlorerBar theme to the Background property of an element:

xmlns:xpbar="clr-namespace:ZonaTools.XPlorerBar;assembly=ZonaTools.XPlorerBar"
...
<Setter Property="Background"
   Value=
   "{DynamicResource 
	{x:Static xpbar:XPlorerResourceKeys.XPlorerBarBackgroundBrushKey}}"/>     

Remark 1: The role of the XPlorerResourceKeys class is explained later in this article.

Remark 2: The name of the static ComponentResourceKey to use when accessing an XPlorerBar element is simply the element name (as shown above) with the Key suffix.

Adding an XPlorerBar to your Application

This sample shows how to create an XPlorerBar with two XPlorerSection and a few XPlorerItem. The first XPlorerSection is set as 'Primary' and the XPlorerBar theme is set to the silver Windows XP theme:

xmlns:xpbar="clr-namespace:ZonaTools.XPlorerBar;assembly=ZonaTools.XPlorerBar"
...
<!-- XPlorerBar -->
<xpbar:XPlorerBar x:Name="ZT_XPlorerBar"
                  xpbar:ThemeManager.Theme="LunaSilver"
                  AllowMultipleExpands="True">

  <!-- Music Tasks -->
  <xpbar:XPlorerSection Header="Music Tasks"
                        HeaderImage="/Images/MyMusic32.png"
                        IsExpanded="True" IsPrimary="True">
    <StackPanel Orientation="Vertical">
      <xpbar:XPlorerItem ItemText="Play all"
                         ItemImage="/Images/PlayAll16.png"
                         Click="XPlorerItem_Click" />

      <xpbar:XPlorerItem ItemText="Shop for music online"
                         ItemImage="/Images/MusicOnLine16.png"
                         Click="XPlorerItem_Click" />
    </StackPanel>
  </xpbar:XPlorerSection>

  <!-- File and Folder Tasks -->
  <xpbar:XPlorerSection Header="File and Folder Tasks"
                        IsExpanded="True" IsPrimary="False">
    <StackPanel Orientation="Vertical">

      <xpbar:XPlorerItem ItemText="Rename this file"
                         ItemImage="/Images/Rename16.png"
                         Click="XPlorerItem_Click" />
      <xpbar:XPlorerItem ItemText="Move this file"
                         ItemImage="/Images/Move16.png"
                         Click="XPlorerItem_Click" />
      <xpbar:XPlorerItem ItemText="Copy this file"
                         ItemImage="/Images/Copy16.png"
                         Click="XPlorerItem_Click" />
      <xpbar:XPlorerItem ItemText="E-mail this file"
                         ItemImage="/Images/MailFile16.png"
                         Click="XPlorerItem_Click" />
      <xpbar:XPlorerItem ItemText="Delete this file"
                         ItemImage="/Images/Delete16.png"
                         Click="XPlorerItem_Click" />
    </StackPanel>

  </xpbar:XPlorerSection>
</xpbar:XPlorerBar>

In the code-behind file, the Click event is handled as follows:

private void XPlorerItem_Click(object sender, RoutedEventArgs e)
{
    MessageBox.Show(
        string.Format("You clicked the '{0}' item.",
        ((XPlorerItem)e.OriginalSource).ItemText));
}

The result is shown below:

Registering and Applying a Custom Theme

To extend the visual appearance of your XPlorerBar, you can create your own theme dictionaries.

The procedure for creating a new theme dictionary is quite simple: in most cases, you will merge with the XPlorerBar.Generic.xaml dictionary, override one or more elements (brushes, geometries, styles, templates, ...) and add it to your project, as shown below:

Then, you need to create your Theme object as follows:

Theme codeProjectTheme = new Theme(
    "CodeProject theme",
    "ZonaTools.XPlorerBar.DemoApp;component/Skins/CodeProjectSkinDictionary.xaml");

And finally, your new theme has to be registered for XPlorerBar objects as shown below:

ThemeManager.RegisterTheme(codeProjectTheme, typeof(XPlorerBar));

You can now use your theme whenever you want by setting (in XAML) the ThemeManager.Theme to the registered name of your theme...

ThemeManager.Theme = "CodeProject theme"

... or, in the code-behind file:

ZT_XPlorerBar.SetValue(ThemeManager.ThemeProperty, "CodeProject theme");

With your custom theme applied, the preceding example becomes:

Remark: As you have seen earlier, the themes can now be applied to any FrameworkElement object. To do so, all you have to do is to register the desired theme to the type of object you want to see themed and apply it to the proper instance. An example is provided in the Extra_ThemeManagement folder: to run this example, modify the App.xaml file of the XPlorerBar.DemoApp project as follows:

StartupUri = "Extra_ThemeManagement/ThemesWindow.xaml"

Using XPlorerSection Template Parts

As you have seen so far, it's really simple to "tune" an existing theme, register it in the ThemeManager and use it in your application. But what if you want to completely redefine an element like an XPlorerSection? How will you restyle the control without modifying or replacing expected behavior?

The answer to the last question is: With Template Parts' help.

The Template Parts allow the configuration of all the binding expressions in the initialization code of the control itself and, this way, the template doesn't need to specify these details anymore. All you have to do then, is to focus on the appearance of your control.

As you have already seen, an XPlorerSection is made up of a header and a content or, from the visual tree point of view, of a ToggleButton and an XPandableDecorator. Two Template Parts are defined in the XPlorerSection class:

• The first one, called PART_HeaderSite (on the ToggleButton), keeps the ToggleButton.IsChecked dependency property synchronized with the XPlorerSection.IsExpanded dependency property.
• The second one, called PART_ContentSite (on the XPandableDecorator), does the same between the XPandableDecorator and the XPlorerSection.

The sample code below shows how the two Template Parts are used in an XPlorerSection control template:

...
<StackPanel Orientation="Vertical">
  <!-- Header -->
  <ToggleButton x:Name="Part_HeaderSite"
                Content="{TemplateBinding Header}"
                Style="{StaticResource HeaderStyle}"/>
  <!-- Content -->

  <xpbar:XPandableDecorator x:Name="PART_ContentSite">
    <Border Background="{TemplateBinding Background}"
            CornerRadius="0,0,4,4">
      <ContentPresenter Margin="{TemplateBinding Padding}"/>
    </Border>
  </xpbar:XPandableDecorator>
</StackPanel>

...

Remark: if you want to see how the two Template Parts are defined, have a look at the OnApplyTemplate method of the XPlorerSection class.

Building an XPlorerBar with Bindings

One of the major new features of the library is that the XPlorerBar is now bindable. Indeed, it's now possible to build dynamically an XPlorerBar with bindings to a data source as an XML file or a collection of observable objects. An example is provided in the Extra_BindingMode folder: to run this example, modify the App.xaml of the XPlorerBar.DemoApp project as follows:

StartupUri = "Extra_BindingMode/BindingsWindow.xaml"

In this example, the data source is an XML file (XPlorerBarXMLFile.xml) presented as shown below:

<?xml version="1.0" encoding="utf-8"?>
<XPlorerBarData>
    <!-- Music Tasks -->
    <XPlorerSectionData Header="Music Tasks" 
	HeaderImage="/Images/MyMusic32.png" IsPrimary="True">
        <XPlorerItemData ItemText="Play all" ItemImage="/Images/PlayAll16.png"/>
        <XPlorerItemData ItemText="Shop for music online" 
		ItemImage="/Images/MusicOnLine16.png"/>
    </XPlorerSectionData>
    ...

The Window.Resources part of the BindingsWindow.xaml file contains the XML data provider and the data templates used to retrieve and organize the data from the XML file:

...
<!-- Data provider -->
<XmlDataProvider x:Key="ZT_XPlorerBarData" 
	Source="XPlorerBarXMLFile.xml" XPath="XPlorerBarData"/>

<!-- Data templates -->
<DataTemplate x:Key="itemTemplate">
    <xpbar:XPlorerItem ItemText="{Binding XPath=@ItemText}" 
			ItemImage="{Binding XPath=@ItemImage}"
                       Click="XPlorerItem_Click"/>
</DataTemplate>
<HierarchicalDataTemplate x:Key="sectionTemplate" DataType="XPlorerSectionData">
    <xpbar:XPlorerSection Header="{Binding XPath=@Header}" 
			HeaderImage="{Binding XPath=@HeaderImage}"
                          IsExpanded="True" IsPrimary="{Binding XPath=@IsPrimary}">
        <xpbar:XPlorerSection.Content>
            <ItemsControl ItemsSource="{Binding XPath=./XPlorerItemData}" 
				ItemTemplate="{StaticResource itemTemplate}"/>
        </xpbar:XPlorerSection.Content>
    </xpbar:XPlorerSection>
</HierarchicalDataTemplate>
...

Finally, the XPlorerBar is declared as follows:

<!-- XPlorerBar -->
<xpbar:XPlorerBar x:Name="ZT_XPlorerBar" xpbar:ThemeManager.Theme="LunaBlue"
                  VerticalAlignment="Stretch" Width="Auto" AllowMultipleExpands="False"
                  ItemsSource="{Binding Source={StaticResource ZT_XPlorerBarData}, 
		XPath=XPlorerSectionData}"
                  ItemTemplate="{StaticResource sectionTemplate}"/>

The result is shown below:

Themes

9 themes are provided with this project :

• 8 are built-in themes (provided with the ZonaTools.XPlorerBar.dll library),
• 1 is a custom theme provided as an example with the demo application.

Enumerated from left to right:

Theme	File	Registered name
-- Built-in themes --
Windows Vista theme	themes/Aero.NormalColor.xaml	Aero
Windows Classic theme	themes/Classic.xaml	Classic
Default Windows XP theme	themes/Luna.NormalColor.xaml	LunaBlue
Olive green Windows XP theme	themes/Luna.Homestead.xaml	LunaOliveGreen
Silver Windows XP theme	themes/Luna.Metallic.xaml	LunaSilver
Windows XP Media Center Edition theme	themes/Royale.NormalColor.xaml	Royale
Zune Windows XP theme	themes/Zune.NormalColor.xaml	Zune
Expression Blend theme	themes/BlendDictionary.xaml	Blend
-- Custom theme --
Code Project theme	skins/CodeProjectSkinDictionary.xaml	CodeProject theme

Remark: The first seven built-in themes enable your XPlorerBar to adapt to the current operating system theme (only if no specific theme is applied to the XPlorerBar or if the ThemeManager.Theme is set to Default).

Project Structure

Here is the library project structure, as seen in Visual Studio's Solution Explorer:

The role of the library classes is explained below:

• ThemeManager.cs - The ThemeManager static class is used for new themes registration and current theme switching.
• XPandableDecorator.cs - The XPandableDecorator class defines the animations used to expand or collapse its content. Inspired by Kevin Moore's Reveal control (from its Bag-o-Tricks [^]), this control has then been adapted to support theming and skinning.
• XPlorerBar.cs - The XPlorerBar class implements the features and the behavior of an XPlorerBar control. An XPlorerBar can only contain XPlorerSection.
• XPlorerItem.cs - The XPlorerItem class implements the features and the behavior of any XPlorerItem nested in an XPlorerSection. An XPlorerItem can contain a text and/or a small icon.
• XPlorerResourceKeys.cs - The XPlorerResourceKeys static class defines a static ComponentResourceKey name for each resource we plan to share with another assembly.
• XPlorerSection.cs - The XPlorerSection class implements the features and the behavior of any section of an XPlorerBar. An XPlorerSection can contain any sort of content as well in its header as in its content. However, two properties allow to easily set its header text and its header large icon.

The Documents folder, reminds you the history of the current release and gives you an overview of the tests executed on the library.

The goal of this quick presentation of the role of the main classes of the ZonaTools.XPlorerBar library is to give you a guide to easily navigate in the source code.

The API's documentation will give you more details on the members of each class of the library.

Finally, the many comments in the source code should give you the keys to quickly understand what is done.

Documentation

The API's documentation was generated with Sandcastle [^] used in combination with Sandcastle Help File Builder [^] (SHFB).

The SHFB project (XPlorerBarDocumentationProject.shfb in the XPlorerBar.Documentation folder) is set to generate a MSDN-like document as an HTML Help 1 file (*.chm).

The documentation project also permits the generation of the documentation as an HTML Help 2 file (*.hxs) or as a Web site (all you need to do is change the 'HelpFileFormat' parameter as shown below and rebuild).

Tools

The project was developed with the following tools:

• Visual C# 2008 Express Edition SP1 [^] 
• SandCastle [^]
• SandCastle Help File Builder [^]
• GIMP v2.4.7 [^]
• Bob Builder v1.0.0.42 [^]

Feedback

This is my first article on The Code Project. So, please let me know what you think.

I hope you'll find this article helpful and instructive. However, if my approach is totally wrong also feel free to let me know.

I definitely want to hear what the community thinks.

Future Work

• Add Visual Studio 2008 designer support
• Add XBAP support
• Add right-to-left layout capabilities
• Create installer (MSI) package

History

• November 5, 2008 - v1.0
  • Initial release
• December 8, 2008 - v1.1
  • Added the Blend theme to the built-in themes of the library.
  • Added a completely new class for theme management which allows to apply themes to any FrameworkElement object. This class replaces the previous ThemeManager class.
  • Removed the now useless ThemeDictionary class.
  • Updated the XPlorerBar class so that an XPlorerBar can now be built dynamically with bindings to a data source.
  • Renamed the ExpandableDecorator class in XPandableDecorator.

You must Sign In to use this message board.

FAQ    Noise Tolerance Very HighHighMediumLowVery Low   Layout Expand Posts & RepliesThread ViewNo JavascriptNo JS + Preview   Per page 102550

Msgs 1 to 25 of 107 (Total in Forum: 107) (Refresh) FirstPrevNext

Change Item Name peug 23:52 11 Jan '10   Hi, How can I change the name of an item from the C # code but not by a XML source (I started in WPF ..) By example, to change item 1 : <!-- Music Tasks --> <xpbar:XPlorerSection Header="Derniers devis ouverts" IsExpanded="True" HeaderImage="/Manager;component/Resources/ssr256.png" IsPrimary="{Binding ElementName=chPrimary, Path=IsChecked}"> <StackPanel Orientation="Vertical"> <xpbar:XPlorerItem ItemText="item 1" ItemImage="/Manager;component/Resources/newssb.png" Click="XPlorerItem_Click" /> <xpbar:XPlorerItem ItemText="item 2" ItemImage="/Manager;component/Resources/newssb.png" Click="XPlorerItem_Click" /> </StackPanel> </xpbar:XPlorerSection> Thanks ! Best regards, christophe Sign In·View Thread·PermaLink Re: Change Item Name peug 4:46 12 Jan '10   In fact, I try to create a list of recent documents opened by another program and place them in XPlorerItem. These documents are stored in the registry. Have you perhaps an idea ? thanks Sign In·View Thread·PermaLink SilverLight version. cesnek 0:32 4 Jan '10   Hello, can anybody migrate this to SilverLight? I definitely cant find ExplorerBar for SilverLight anywhere (paid or free). Sign In·View Thread·PermaLink Is there a Windows Forms Version available too? Schudi 11:10 13 Dec '09   I never worked with WPF but build everything with Windows Forms so far. I really like you Explorer Bar and would realy like to use it in my apps. So, is there any chance to use this with windows forms as well? Sign In·View Thread·PermaLink Not stretching in Grid with GridSplitter cesnek 5:02 21 Oct '09   Hello, this component realy rocks, but. When I include XPlorerBar in Grid it not horizontally stretchig. I already try ScrollViewer, but no luck. Pleas help!!    <Grid>                   <Grid.ColumnDefinitions>                         <ColumnDefinition Width="Auto"/>                         <ColumnDefinition Width="Auto"/>                         <ColumnDefinition Width="*"/>                   </Grid.ColumnDefinitions>                   <Grid.RowDefinitions>                         <RowDefinition></RowDefinition>                   </Grid.RowDefinitions>             <my:XPlorerBar Grid.Row="0" Grid.Column="0" VerticalAlignment="Stretch" AllowMultipleExpands="True"   HorizontalAlignment="Center" </my:XPlorerBar>             <GridSplitter Grid.Row="0" Grid.Column="1" Height="Auto" Width="3" HorizontalAlignment="Stretch"></GridSplitter>             <....>    </Grid> Sign In·View Thread·PermaLink 1.00/5 (1 vote) how to use this? rothj0hn 18:20 30 Sep '09   im a newbie programmer.. can i use this in vb.net 2008.. how can i attached it in my application? kindly discuss it step by step.. Sign In·View Thread·PermaLink 2.00/5 (1 vote) best (-_-) 23:54 23 Sep '09   very very good Sign In·View Thread·PermaLink Re: best Olivier Simon 13:21 26 Sep '09   Thanks a lot for your kind words. Regards, Olivier Simon My blog [^] Sign In·View Thread·PermaLink Fantastic! firemagus 7:26 19 Sep '09   Elegant and extendable. Great job! @ngelo Sign In·View Thread·PermaLink Re: Fantastic! Olivier Simon 13:20 26 Sep '09   Thanks for the feedback. I am glad you enjoy the component. Regards, Olivier Simon My blog [^] Sign In·View Thread·PermaLink Can't wait to use this Ant2100 10:55 25 Aug '09   This control is the best! Can't wait to try it out Thanks, Anthony Check out my desktop conversion software for Windows - www.universalconverter.net Sign In·View Thread·PermaLink Re: Can't wait to use this Olivier Simon 0:59 31 Aug '09   Thanks a lot for the feedback. I am glad you like it. Regards, Olivier Simon My blog [^] Sign In·View Thread·PermaLink Missing files in download xzz0195 5:34 28 Jul '09   Error 2 File 'Extra_BindingMode\BindingsWindow.xaml' cannot be found. XPlorerBar.DemoApp Error 3 File 'Extra_ThemeManagement\ThemesWindow.xaml' cannot be found. XPlorerBar.DemoApp Error 4 File 'Skins\CodeProjectSkinDictionary.xaml' cannot be found. XPlorerBar.DemoApp Error 5 The project file contains a property value that is not valid. XPlorerBar.DemoApp Error 7 File 'Themes\Aero.NormalColor.xaml' cannot be found. XPlorerBar.Library Error 8 File 'Themes\BlendDictionary.xaml' cannot be found. XPlorerBar.Library Error 9 File 'Themes\Classic.xaml' cannot be found. XPlorerBar.Library Error 10 File 'Themes\Generic.xaml' cannot be found. XPlorerBar.Library Error 11 File 'Themes\Luna.Homestead.xaml' cannot be found. XPlorerBar.Library Error 12 File 'Themes\Luna.Metallic.xaml' cannot be found. XPlorerBar.Library Error 13 File 'Themes\Luna.NormalColor.xaml' cannot be found. XPlorerBar.Library Error 14 File 'Themes\Luna.Style.xaml' cannot be found. XPlorerBar.Library Error 15 File 'Themes\Royale.NormalColor.xaml' cannot be found. XPlorerBar.Library Error 16 File 'Themes\XPlorerBar.Generic.xaml' cannot be found. XPlorerBar.Library Error 17 File 'Themes\Zune.NormalColor.xaml' cannot be found. XPlorerBar.Library Error 18 The project file contains a property value that is not valid. XPlorerBar.Library Sign In·View Thread·PermaLink Re: Missing files in download xzz0195 5:49 28 Jul '09   My bad, turns out the the extractor program Ultimate zip was not putting the conent of the subdirectories into the subdirectory folder (even though it created the subdirectory folder). To fix this I put the zip package into the root folder I wanted and clicked "Extract to here" that did it. Strange. Sign In·View Thread·PermaLink Congratulations! xzz0195 6:01 28 Jul '09   Thank you for posting this, this is a very nice demonstration/framework for bringing WPF oriented look and feel for the common man. You've provided the nice design, we just have to provide the function. This is a very nice bit of work, Thank you! Sign In·View Thread·PermaLink Re: Congratulations! Olivier Simon 1:00 31 Aug '09   Thanks a lot for the feedback. Regards, Olivier Simon My blog [^] Sign In·View Thread·PermaLink Works in Xbap? cycleguy 8:31 10 Jul '09   Hello, First, awesome looking control! I am trying to build this control into an xbap project. It renders fine at design time, but when I execute it and it is trying to render the explorer bar, it bombs with a security exception. Its complaining about a bitmap effect it is trying to perform. Is there anything in this control that would prevent it from running in an xbap? I currently have the xbap running in Full Trust mode. Thanks Harold Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: Works in Xbap? cycleguy 8:33 10 Jul '09   OK, just saw under "Future Work" Xbap support will be added... any time frame for this? Would really be helpful. Thanks Harold Sign In·View Thread·PermaLink Re: Works in Xbap? cycleguy 8:46 10 Jul '09   I just went into the source code, found where the bitmap effect was being used in the "Luna.Style.Xaml" file, removed it and now it works fine in an xbap. Is that really it? Thanks! Harold Sign In·View Thread·PermaLink Re: Works in Xbap? cesnek 4:53 21 Oct '09   Yes! It simple comment bitmapeffect works for me. God bless open source Sign In·View Thread·PermaLink Thanks and question. daonin 12:39 3 Jun '09   Firstly, thanks a lot for your article! It`s very helpful. But I need your advice. I want to put current select into closed section. Like that: [pic] Is it doable? Sign In·View Thread·PermaLink ObjectDataProvider clinton van ry 5:23 2 May '09   Firstly this is a great article and a very nice component. I am very new to WPF and was wondering if you could provide a sample that uses objects. I have had a look at the SportsData sample you provided but i cant figure out how to do that from code? I have pasted the sample sports classes. public class Player { public string Name { get; set; } } public class Sport { private ObservableCollection<Player> m_Players; public string Name { get; set; } public string Image { get; set; } public ObservableCollection<Player> GetPlayers() { m_Players = new ObservableCollection<Player>(); if (this.Name == "Tennis") { m_Players.Add(new Player() { Name = "Federer" }); m_Players.Add(new Player() { Name = "Tsonga" }); m_Players.Add(new Player() { Name = "Djokovic" }); } else if (this.Name == "Football") { m_Players.Add(new Player() { Name = "Benzema" }); m_Players.Add(new Player() { Name = "Messi" }); m_Players.Add(new Player() { Name = "Gerrard" }); } else // Basketball { m_Players.Add(new Player() { Name = "Parker" }); m_Players.Add(new Player() { Name = "Bryant" }); m_Players.Add(new Player() { Name = "Magic Johnson" }); } return m_Players; } } public class Sports { List<Sport> m_sport; public Sports() { m_sport = new List<Sport>(); m_sport.Add(new Sport() { Name = "Tennis", Image="/Images/Move16.png" }); m_sport.Add(new Sport() { Name = "Football", Image = "/Images/Move16.png" }); m_sport.Add(new Sport() { Name = "Basketball", Image = "/Images/Move16.png" }); } public List<Sport> GetSports() { return m_sport; } } Sign In·View Thread·PermaLink very good zhujinlong19840913 21:49 16 Apr '09   very good Sign In·View Thread·PermaLink Re: very good Olivier Simon 11:38 20 Apr '09   Thanks a lot for that. I am glad you like it. Regards, Olivier Simon My blog [^] Sign In·View Thread·PermaLink Bind a particular section only. Naks83 2:54 27 Jan '09   Hi I have the xplorer bar added to my project. The section and the items are defined in the xaml itself. There are 6 sections in total. Now, I need to populate ONE of the sections with a list retrieved from the database. Here's what I did 1. Define the content for the section. <xpbar:XPlorerSection.Content> <ItemsControl ItemsSource="{Binding}" ItemTemplate="{StaticResource itemTemplate}"/> </xpbar:XPlorerSection.Content> 2. Added the Item Template for the Xplorer Items <DataTemplate x:Key="itemTemplate"> <xpbar:XPlorerItem ItemText="{Binding Path=ContractStatus}" Command="local:MainWindow.OpenReportsCommand"/> </DataTemplate> 3. Set the ItemsSource for the bar to the collection I want to bind to. XPlorerBar.ItemsSource = contractStatusCollection; But I get an error saying that the Items must be empty before using ItemSource - that's because I have predefined the sections. So is there a way to have both - Define sections in xaml and bind one of them dynamically? Thanks Nakul Ringshia Sign In·View Thread·PermaLink

Last Visit: 16:02 9 Feb '10     Last Update: 16:02 9 Feb '10 12345 Next »