views:

360

answers:

2

As part of my on-going attempt to come to terms with WPF/XAML, I've become interested in the application of fluent interfaces to UI coding.

I am aware of Fluent Silverlight (http://code.google.com/p/fluent-silverlight/), but I can't seem to find anything equivalent for WPF.

Just as a personal note, I'm finding it very difficult to buy into doing everything in a combination of XAML and C#/MVVM. It just seems to me that there are certain aspects of UI programming (e.g. data binding) that are better expressed in code than in declarative XAML.

A fluent WPF interface would seem to be just the thing to accomplish these goals.

+1  A: 

On a recent podcast of Herding Code: http://herdingcode.com/?p=212 one of the guests discusses that they attempted a fluent interface for creating WPF UIs. It's possible one of them could make what they have done available.

Incidentally, this same podcast and the one before it (http://herdingcode.com/?p=208) speak to your concerns about code first vs. view first and why it is advantageous to concentrate on xaml.

The arguments for are primarily about making UIs "Blendable" (being able to design them in Microsoft Expression Blend) by a designer in addition to the testability of your code. A code-based approach sort of diminishes this ability if you aren't very careful.

You are not alone in your misgivings. Hopefully these podcasts will help you make a decision.

Anderson Imes
Thanks.I have listened to both those podcasts, and actually decided to investigate fluent silverlight because of them.WPF contains lots of cool things -- its just a matter of figuring out how best to use (and package) them.At the risk of dating myself, I had thought about an MFC equivalent to WPF, but the fluent interface seems like a better approach.Does anybody else know of other balanced appraisals of WPF? I.e. neither completely negative nor completely blindly accepting?
kmontgom
I've not heard of much. Most people are embracing Xaml that I've ran across. It's really bad at all. I like it a lot now, personally. I think if I had to go to a fluent interface I would likely find it cumbersome, if you can believe that.
Anderson Imes
A: 

Fluent API for building Commands in WPF http://code.google.com/p/present/

Thejuan