Hello,
I am trying to use Telerik's WPF GridView control in a MVVM application. I have two general questions:
1) It seems that the XAML/WPF approach to MVVM requires the view to both a.) databind to the viewmodel, and b.) sink events from the viewmodel (that is, the view must respond to events from the view model). Given that the Telerik WPF DataGrid obviously resides in the view, where does Telerik document the complete list of WPF DataGrid properties and methods? Surely we can't be expected to infer the list of properties and methods from the samples? Yet I cannot find what I normally think of as documentation.
2) In the stock MVVM definitions and explanations I find on the internet, it seems that the MVVM advocates claim there is a "clear separation" of concerns between the view, the viewmodel, and the model. But in the stock MVVM implementations, I find that the view's XAML invariably contains column names in the grid declaration. That seems to violate MVVM, no? In these implementations, the view seems to be overly concerned with the model. Wouldn't it be best if the view only knew how to query the collection of column names from the viewmodel? Then you wouldn't have to modify the view (that is, the XAML) every time a user requested a new column.
Thanks. I apologize in advance if these newbie-ish questions have been asked elsewhere; I queried the forums and could not find answers.
I am trying to use Telerik's WPF GridView control in a MVVM application. I have two general questions:
1) It seems that the XAML/WPF approach to MVVM requires the view to both a.) databind to the viewmodel, and b.) sink events from the viewmodel (that is, the view must respond to events from the view model). Given that the Telerik WPF DataGrid obviously resides in the view, where does Telerik document the complete list of WPF DataGrid properties and methods? Surely we can't be expected to infer the list of properties and methods from the samples? Yet I cannot find what I normally think of as documentation.
2) In the stock MVVM definitions and explanations I find on the internet, it seems that the MVVM advocates claim there is a "clear separation" of concerns between the view, the viewmodel, and the model. But in the stock MVVM implementations, I find that the view's XAML invariably contains column names in the grid declaration. That seems to violate MVVM, no? In these implementations, the view seems to be overly concerned with the model. Wouldn't it be best if the view only knew how to query the collection of column names from the viewmodel? Then you wouldn't have to modify the view (that is, the XAML) every time a user requested a new column.
Thanks. I apologize in advance if these newbie-ish questions have been asked elsewhere; I queried the forums and could not find answers.