Comments on: DataModel and ViewModel http://www.thoughtclusters.com/2007/12/datamodel-and-viewmodel/ Software Development and Management Tue, 09 Mar 2010 05:00:09 -0800 http://wordpress.org/?v=2.9.2 hourly 1 By: Krish http://www.thoughtclusters.com/2007/12/datamodel-and-viewmodel/comment-page-1/#comment-463 Krish Mon, 18 May 2009 14:25:00 +0000 http://www.thoughtclusters.com/2007/12/datamodel-and-viewmodel/#comment-463 My article is meant to be more generic than the other articles which are more .NET specific. Basically a ViewModel is a data representation that is specific to a particular view, while a standard Model (or DataModel) is less specialized. How you expose the data depends on the implementation and the platform. <br /><br />A ViewModel can have different implementations and even different reasons. For example, one reason for using a ViewModel is that instead of a developer, it might be a UI designer who is working with the view. My article is meant to be more generic than the other articles which are more .NET specific. Basically a ViewModel is a data representation that is specific to a particular view, while a standard Model (or DataModel) is less specialized. How you expose the data depends on the implementation and the platform.

A ViewModel can have different implementations and even different reasons. For example, one reason for using a ViewModel is that instead of a developer, it might be a UI designer who is working with the view.

]]> By: Anonymous http://www.thoughtclusters.com/2007/12/datamodel-and-viewmodel/comment-page-1/#comment-462 Anonymous Mon, 18 May 2009 09:04:00 +0000 http://www.thoughtclusters.com/2007/12/datamodel-and-viewmodel/#comment-462 The DataModel you are describing here does not seem to be the same kind of DataModel that Dan Crevier has used in the DM/V/VM pattern. In his version, the DM exponses data in a form that is easily consumed by WPF using DataTemplates. Is this intentional, and is the DM you are describing an entirely different beast? The DataModel you are describing here does not seem to be the same kind of DataModel that Dan Crevier has used in the DM/V/VM pattern. In his version, the DM exponses data in a form that is easily consumed by WPF using DataTemplates. Is this intentional, and is the DM you are describing an entirely different beast?

]]>