﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Intersoft Community - ClientUI - Need advice on Editable Grids</title><link>http://www.intersoftsolutions.com/Community/ClientUI/Need-advice-on-Editable-Grids/</link><description /><generator>http://www.intersoftsolutions.com</generator><language>en</language><copyright>Copyright 2002 - 2015 Intersoft Solutions Corp. All rights reserved.</copyright><ttl>60</ttl><item><title>Need advice on Editable Grids</title><link>http://www.intersoftsolutions.com/Community/ClientUI/Need-advice-on-Editable-Grids/</link><pubDate>Wed, 19 Jun 2013 03:08:21 GMT</pubDate><dc:creator>yudi</dc:creator><description>&lt;blockquote&gt;... The ClientEditingEditViewModel has all the code for the preparing new rows, inserting, canuseradd etc. It seems like the code from this module for the methods and properties for an editable grid are just copied into each ViewModel that handles a grid rather than creating a generic ViewModel that handles all grids...&lt;/blockquote&gt;
&lt;p&gt;&lt;span style="color: rgb(31, 73, 125);"&gt;Yes, I agree that implementing such pattern, to create a generic ViewModel that handles generic on all grid, would be better than copied the methods and properties into each ViewModel.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color: rgb(31, 73, 125);"&gt;Intersoft ClientUI MVVM Data Application (WPF) project template has implemented this pattern. It has EditableGridViewModelBase and EditableGridViewModelGenericBase (this class is located in [ProjectName]\ViewModels.Infrastructure). Hence, we can simply inherit from those classes and use it in our ViewModels, for example: ProductsViewModel.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color: rgb(31, 73, 125);"&gt;Thanks again for your message. The ideas and suggestions of innovative, thinking people are always welcome.&lt;/span&gt;&lt;/p&gt;</description></item><item><title>Need advice on Editable Grids</title><link>http://www.intersoftsolutions.com/Community/ClientUI/Need-advice-on-Editable-Grids/</link><pubDate>Tue, 18 Jun 2013 15:08:41 GMT</pubDate><dc:creator>BillGower</dc:creator><description>&lt;p&gt;in my app i have multiple places where i will be using editable grids. The ClientEditingEditViewModel has all the code for the preparing new rows, inserting, canuseradd etc. It seems like the code from this module for the methods and properties for an editable grid are just copied into each ViewModel that handles a grid rather than creating a generic ViewModel that handles all grids. Am I correct in thinking that?&lt;/p&gt;
&lt;p&gt;example&lt;/p&gt;
&lt;p&gt;CustomerEditViewModel / ProductsEditViewModel / CategoriesEditViewModel&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;All of these would start out with all the properties and methods that are in ClientEditingViewModel and each would have specific methods and properties for the applicable model. Is that correct?&lt;/p&gt;</description></item></channel></rss>