How to allow full customization with a Resource Dictionary? (Part IV)

I know I’m a bit late with this, but I had no time at all to post this earlier. So, with no more delays I present you the source code for the customization application I promissed.

Remember, this is a pretty simple example of how to implement something like this.

Lets see why this method is so good:

It allows designers to completely customize the application for each theme

It allows you to give functionality per theme

Desn’t require you to recompile your application each time you want to change something in a theme (in the real world apps this is a very important fact and I had to deal with that when building the Imokapa Slideshow Application).

Complete abstraction between visual and logic

You only have to plan for features and the designer only needs to implement them visually

Each control is planned to detail divided in features, this allows the designer to choose wich is the right feature for each visual or logical implementation

In the sample provided I wanted to show a bit of the last point, in the default template (contained in the generic.xaml file) I have 4 buttons and in the vista arrows ResourceDictionary I have only 2 buttons that implement back and forward. This permits the control to be reused for othe purposes without having to re-write it’s logic! Great, huh?