Hi MS Developers,
I'm discovering the MVVM pattern, and something is bothering me:
The separation of the view from the business Model and business logic is a very cool thing, and I wuld like to use this strength in my programs for portability over mono.
But I am having questions about this:
I would like to manipulate only List, Dictionaries etc from my business logic, and all the examples I found are using ObservableCollections directly from the ViewModel when they need to bind a list to the view, which means that when they add an item to their collection, they add it in the ObservableCollection, which is an issue for me, as I would like to get rid of all view-related classes of .NET in my program.
I may be mistaking, as I don't yet understand all the concepts of the MVVM pattern, but is there a way of manipulating only normal collections (no INotifyPropertyChanged, no IObservable etc) in the main logic of my program, and, still keep the MVVM "binding power"? (An observableCollection that keeps a reference on a normal collection and updates itself when changes are made on the collection..?)
Maybe by adding a new layer in the MVVM pattern between the ViewModel and the Model?
I hope I'm explicit enough with my issue
Thanks in advance =)