Chaps, I have some news on this subject.
After talking to the client go-between on just when they needed in the way of custom styling the SL3 app, it seems that the level of skinning provided by the toolkit themes is way beyond their needs. They need about 6 different major parts of the various major controls customised (the background, the footer, header, etc). They don't need the appearance of all text, combos, list, etc controls customised. I already had the common properties of important controls styled in the App.xaml, so I moved those setters into a class I called 'ApplicationBinder' which exposed the various Brushes and misc custom settings as dependency properties. That binder class is a global resource in the App.xaml so that it was available to all controls. Once that is done, you can dynamically change the brushes and the binding will update the appearance all over the place where the controls are bound. There is no wizardry in this, but it's a reminder of the power of binding. Rather than put global styles in App.xaml, put them in a global resource class that you can bind to from anywhere. You then have an instant lightweight dynamic skinning. I plan to return to the toolkit themes and use them later once I'm on SL4. But using simple binding to a global resource class is a miracle quick fix for now. Cheers, Greg
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
