Summary: All application procedures are not open to display and interaction.
View: Responsible for creating interface elements, interface layout, responsible for receiving external interaction, and notify control processing.
Control: is responsible for controlling the actual data of the view element and is responsible for dealing with the actual interactive process of view sending over. Responsible for getting or sending data from model.
Model: Saves the data and responds to the control's request. So ==>View:1, there should be a way to initialize the creation element: Initui. 2. All elements can be exposed to control to show actual data. 3 provides an outer-to-interface and executes an interface function, which is actually implemented by control. Protocal:onclickcontrol:1: You should have view. If you can perform the initial method of view first. and get the view. Self.view=xxx ==>getsomecontrol. 2: Implement view interface <pagePortocal> 3 implement some system encapsulated elements interface such as. iOS ' s protocal. Eg:table delegate.model:getlist, Updatesomemode., observe data changes. and send notifications to subscribers. So, any control, just create an instance of the view and implement the interface. Can take over view very well. You can even manage multiple view.The view is independent and does not depend on control.Can actually be generalized to most of the program structure. such as. Web.html is responsible for creating and laying out. and is responsible for post data to the service side processing. The service side handles interactive events. ASP. NET, you can know the elements of any view and display the data. Such as
MVC for iOS
