Adding a modern spark to your WPF apps, with WPFSpark

Today's WPF Wednesday post is a revisit to a project from Ratish Philip that we highlighted nearly four years ago, Adding some spark to your next WPF project with WPFSpark, a project that's back and updated too.

WPFSpark will help you give your WPF application a much more modern feel...

image

WPFSpark v1.2

At last, it's here! After a really long gap of nearly 4 years, I am happy to announce that the next version of WPFSpark is finally released. Smile | <span class=:)" align="top">

What's new in WPFSpark v1.2

In this section I will be providing a summary of new features and modifications made to the WPFSpark controls so that you can adapt your code quickly and integrate new features with ease. For WPFSpark v1.1, I had written several articles, explaining in detail, how each of the controls was designed and implemented. You can see those articles here (WPFSpark: M of N series). I intend to update these articles as soon as possible. For the time being, this article should bring you up to speed. All the code has been ported to .NET framework 4.6.1 using C# 6.0.

SprocketControl

image

ToggleSwitch

image

FluidWrapPanel

image

SparkWindow

image

FluidPivotPanel

image

FluidProgressBar

image

FluidStatusBar

image

Using WPFSpark v1.2 in your code

WPFSpark v1.2.0.1 is available in NuGet. You can obtain it here. Alternatively, you can add it to your project from Visual Studio using the Manage NuGet Packages option (Just right click on your project in the Solution Explorer and click on Manage NuGet Packages).

If you are interested in getting your hands dirty with code, you can access the WPFSpark source code in GitHub. I have moved the code from CodePlex to GitHub as I feel it is easier to manage your code in GitHub. Also the code is available under MIT License.

[Click through for the entire post]



Tags:

Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
    Unsubscribing
    Subscribing

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.