Comments on: Parts & States Model with VisualStateManager (Part 1 of 4)

By: FlickrViewr Updated for Beta2 | karen corby's fabulous blog

FlickrViewr Updated for Beta2 | karen corby's fabulous blog — Thu, 16 Sep 2010 18:11:25 +0000

[...] to say I’ve updated my FlickrViewr for Silverlight Beta2. (All of the controls now use VisualStateManager, [...]

By: An Early Look – VisualStateManager for WPF | karen corby's fabulous blog

Thu, 16 Sep 2010 18:11:04 +0000

[...] Gossman, one of the awesome Silverlight and WPF architects, just blogged a prototype of VisualStateManager for [...]

By: Silverlight Bits&Pieces: The First Steps with Visual State Manager « AJ’s blog

Sun, 24 Jan 2010 16:29:14 +0000

[...] A more complex example: http://scorbs.com/2008/06/11/parts-states-model-with-visualstatemanager-part-1-of/ [...]

By: Pietro Brambati Blog : Silverlight 2 – (alcune) risorse

Pietro Brambati Blog : Silverlight 2 – (alcune) risorse — Mon, 22 Dec 2008 10:03:20 +0000

[...] & States Model with VisualStateManager (part 1, part 2, part 3, part [...]

By: Nathan

Nathan — Tue, 28 Oct 2008 15:18:21 +0000

The link to part 2 isn’t working :(

By: Fahim Ilyas

Fahim Ilyas — Mon, 30 Jun 2008 07:05:10 +0000

Very interesting, anybody looking for customization of the look and feel of application should read this because this article truly reflects what look less control means and how easy it is to create a custom look and states for a control in silverlight.

By: Neil Mosafi

Neil Mosafi — Mon, 16 Jun 2008 08:47:17 +0000

Thanks for the response Karen. I do really like the states model and the blend support; I remember when working with a graphic designer on a previous WPF project we (the devs) ended up doing most of the work on control state transitions cos the old WPF way of doing things wasn’t very designer friendly at all.

I’ll be looking forward to Part 2!

By: Karen

Karen — Fri, 13 Jun 2008 00:49:18 +0000

@Neil: All great questions! I’ll dig much more into the WPF story for Parts & States Model in the final post of this series. But the short version is: Blend’s support for triggers in WPF controls is not going to change – you’ll still have the support it has today. Moving forward, we will be adding VSM to WPF as well, which means that you’ll be able to more easily move SL templates to WPF controls. At that point, you’ll also have the parts & states Blend experience for WPF too.

The naming convention in Silverlight is slightly different – we are not using the underscore PART_ convention.

Thanks for the skin recommendation – CheckBox is a good control to give an intro on, since it has multiple state groups. But I promise to do a post later that goes into a more complex skin.

By: Neil Mosafi

Neil Mosafi — Thu, 12 Jun 2008 11:28:03 +0000

Great post Karen and well explained.

A couple of questions from a WPF developer… firstly I understand that the state model will be added to WPF in the future – does this mean we should stop using Triggers in our WPF application and use States instead if we want Blend to support skinning our apps? Will WPF’s inbuilt controls get states added to them?

Secondly, WPF already has the Parts model and it’s recommended by Microsoft to prefix all Parts with the PART_ prefix. Is this still recommended in Silverlight?

Oh – how about in Part2 skinning another control, I’ve already seen lots of examples on CheckBox skinning!

Cheers!
Neil

By: nemiso

nemiso — Thu, 12 Jun 2008 05:03:42 +0000

this is a relly good post;
I really want to know how to make a custom state.
I’m looking forward to seeing your next post.