I recently asked a StackoverFlow question about MVC: Can an MVC template / architectural template be used in desktop development?
Based on the answer I received, I began a study on how this will be implemented in a Windows form application. I came to the following CodeProject article: http://www.codeproject.com/KB/cs/model_view_controller.aspx
In the comments below, some users claim that (although this is a good article), this is actually an observer pattern. First, but less importantly, the question is, does anyone agree or disagree with this, and why?
Regarding the second and more important question: I am trying to create a small task list program in .NET. It will be very tiny and hopefully fast. Overall, what would be the best architecture for such a project? Observer pattern or MVC pattern? Or another template?
thank
(This article is not an example of MVC AFAIK for the simple reason that there is no controller .. it is closer to .net data binding if you ask me.)MVC Observer. MVC . , . "" , (Pure MVC). ( /). MVC - . , MVP, , / .
Observer . , , .net
, , ... /
, .
mvc (http://en.wikipedia.org/wiki/Model-view-controller) / (http://en.wikipedia.org/wiki/Observer_pattern#Subject), (http://en.wikipedia.org/wiki/Observer_pattern#Observer). . : mvc http://webcourse.cs.technion.ac.il/234321/Winter2005-2006/ho/WCFiles/08-Design-Patterns.ppt
, MVC. . .NET , , .
MVC , , , , . MVC - , . , mvc. : MVC-. .
===========
: ? , . , . , , , .
If I were you, I would start on the model side first, and then take things from there.