Reduce XAML verbosity
A lot of things that can't be done using markup extensions require a tremendous amount of disgusting XAML. Some things could be as simple as applying the ContentProperty attribute intelligently. For example, why do I need to specify Setter.Value? Setter's default content property should already be its Value property. Same with DataGrid.Columns. DataForm is an improvement in Silverlight but still not perfect. A simple label/field layout should be a first class use case in XAML.
Setter really should have had the ContentProperty attribute in the first place.
Although XAML should be a designer tool, its verbosity should be minimized as much as possible.
And BTW @mike.strobel, how for god sake can take to implement this feature in a setter + tests +++!?!?
C'mon this is pure ignorance.
Thomas Levesque commented
Yes, I've always been annoyed by that Setter.Value thing...
So, are you asking for something that is conceptually between a visual designer and XAML? I'm not sure I understand the utility of that. Please help me understand the request.
The new Xaml DOM and parser extension points in .NET 4 (System.Xaml) will enable you to create your own syntax and parser. However, I think implementing such a syntax is a feature better left to the community so the WPF team can focus on making the framework more extensible in other areas.