For WPF Wednesday (I think Wednesday is going to be a kind of a rotating theme day... from WPF, to Web, "Wild" and Weird...) we're going to take another look at the Extended WPF Toolkit project. It's been nine months since we last looked at it, Today's toolkit time with the Extended WPF Toolkit and since then we've gotten a new version with a bunch of new controls.
Also last time we didn't look at the cool sample app that's included in the source tree...
Want an easier way to install the Extended WPF Toolkit?The Extended WPF Toolkit is available on Nuget.
What's in the 1.5.0 Release?
- CheckListBox - New Control
- CollectionEditor - New Control
- CollectionEditorDialog - New Control
- DropDownButton - New Control
- MultiLineTextEditor - New Control
- PrimitiveTypeCollectionEditor - New Control
- PropertyGrid - Beta
- Wizard - New Control
So as you can see, v1.5 has a number of new cool things to play with.
For example the Wizard control. Many app's use them and many dev's re-invent that wheel when they do. This control looks simple, yet configurable enough, that maybe we don't need to re-invent it anymore (and even if we do, since the source is available, we don't have to start from scratch!
Then there's the some of the other controls, new and old, too;
Like one of my favorite, the calculator control
Or the watermark textbox
Or the new WPF Property Grid;
One thing about these samples... They are "live." They are not static examples or screenshots, but instead live, working code.
Speaking of the Sample app. I thought it very cool that the sample app used Prism. Prism is meant to help you build composite applications, separating the shell and components and allowing them all to evolve independently.
So what does that mean? It means that what you're seeing above is a simple shell that hosts modules that do the work. That once created, you're pretty much done with the shell and you can focus on the specific modules.
The Sample shell is a simple host for the sample modules. In this case modules are added to the shell via the app.config.
If we take a peek at the wizard sample module;
Okay, okay, I know, enough samples. Here's a snap of the Toolkit project itself;
As you can see the Toolkit project is well segmented by control, making it very easy for you to find the source for the control of interest. For example, for the wizard control;
If you're building WPF applications or re-usable controls for them, this toolkit is one you should check out...