AFAIK / understand,
Decoupling presentation logic from application logic is the basic motive behind the Document-View architecture used by MFC applications. For example, assume we use the App Wizard to create an application called Demo (accepting all of the default features). Among the classes generated are CDemoDoc and CDemoView derived from CDocument and CView, respectively:
class CDemoDoc : public CDocument { ... }; // in DemoDoc.h
class CDemoView : public CView { ... }; // in DemoView.h
In C#, there are options like MVC & MVVM as couple of common ones to achieve it. Mostly, winforms use MVC and WPF apps use MVVM architecture to segregate data model, presentation layer and business logic.
Now to take MVC in comparison for example here:
- MVC stands for Model (handles data) - View (responsible to show data to user) - Controller (responsible to get user input and convert into actions on models)
- MFC Document-View has only 2 components. Document is equivalent to model here. View is responsible for both view document and connect to user inputs.
So, high level, MFC View is equal to View-Controller of MVC pattern.
Submit an article or tip