Presentation Model Thoughts

re: Presentation Model Thoughts

Michael Swanson — Mon, 01 Nov 2004 23:30:00 GMT

Ray...Sounds like an implementation of the Memento design pattern, which works well in Undo/Redo situations.

re: Presentation Model Thoughts

Ray Klaassen — Mon, 01 Nov 2004 23:26:00 GMT

The business objects that I showed you when you visited (Rocky Lhotlka's CSLA framework) has all the rules in the business object but also implements multi-level undo. The initial state of the business object is serialized and persisted, while databinding handless changes to the "current" business object. If you want your UI to allow the user to set "bookmark" point, the framework serializes the object again allowiing the user to save changes, undo to the bookmark or undo to the initial state of the business object.

re: Presentation Model Thoughts

Michael Swanson — Fri, 29 Oct 2004 07:47:00 GMT

Thanks for the feedback, Fredrik. I like your idea of an XML mapping between the presentation and its associated behavior. However, I'm trying to leverage the Visual Studio 2005 IDE where possible (for the developer productivity benefits), and forcing a developer into an XML mapping file might be a little more than they would bargain for. On the other hand, it might be a good excuse to write a designer for Visual Studio that handles the dirty work visually. Now you have me thinking. :)

re: Presentation Model Thoughts

Fredrik Normén — Fri, 29 Oct 2004 07:27:00 GMT

Hi Michael,

For a week ago I talked to Fowler about removing the synchronizer method to use a UI mapper instead to fill our domain objects, he thought that sounds like a good approached. The problem with the Presentation Model is that we have to write our synchronizer method for getting the user inputs and also setting the value of our controls. With a UI mapper we could easy map controls to any kind of object and specify the mapping in an XML file. By doing this we don't need to manually create the synchronizer method, instead we could use a UI mapper that will set the Presentation Model's property for us.