Model-see, Model-do, and the Poo is Optional

Dew Drop - May 22, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 22, 2008 | Alvin Ashcraft's Morning Dew — Thu, 22 May 2008 17:26:29 GMT

PingBack from http://www.alvinashcraft.com/2008/05/22/dew-drop-may-22-2008/

Leveraging Freezables to Provide an Inheritance Context for Bindings

Ask Dr. WPF — Fri, 23 May 2008 22:51:29 GMT

Mike Hillberg has some great observations about WPF application architecture as it pertains to model interaction in his "Model See Model Do" post. I am very much in agreement wi ...

re: Model-see, Model-do, and the Poo is Optional

Eisenberg — Fri, 23 May 2008 23:09:04 GMT

Mike,

Great post! This is very similar to the way that Caliburn's ActionMessage and EventMessage systems work. I've been working with WPF in this way for quite a while and found it a very pleasant way to develop. Caliburn also works with any event on any control type. It can automatically determine input parameters, run code asynchronously (with callbacks), databind method return values and handle exceptions. All these features are also available for the CanExecute scenarios, except the UI isn't limited to only disabling itself if the action isn't available. It can also hide and collapse, as well as have any other behavior that the develop wishes to plug.

That's just one of Caliburn's feature areas. I'd love for you to check it out and give me some feedback. The project web site is http://caliburn.tigris.org/

re: Model-see, Model-do, and the Poo is Optional

SilverSideDown — Thu, 16 Apr 2009 18:39:06 GMT

Looks like Caliburn has moved to

http://www.codeplex.com/caliburn