Page 1 jumps to page 2, after page 2 Click button, the content of page 1 is changed. Actually using protocol (that is, interface in C #), convert page 1 viewcontroller to protocol incoming page 2 Viewcontroller, very similar to what we developed in C # will _ Viewcontroller into the interface into other custom controls, etc., is actually placed in page 2 a reference, in Swift this procedure is called a delegate, C # also. This idea should be an embodiment of interface-oriented programming, using interface to solve the coupling. I can now slowly understand that the Viewcontroller and xib in Swift are equivalent to the XAML and CS in the UWP, but we use MVC and MVVM in the UWP to encapsulate a layer of viewcontroller, This is purely the name of the two different languages, will make me a little dizzy. But from the perspective of learning Swift now, Viewcontroller is a very basic thing, mainly used to draw the interface and the pure UI, after the later function, it must be again lunar layer to do the UI logic of the package, is equivalent to the viewcontroller of MVVM in the UWP.
Reverse values from UWP to swift-pages
