Advantages of WPF--XAML

Advantages of WPF--XAML

 

Body:

 

2. What are the advantages of XAML?
The previous section has revealed several advantages of XAML:
• XAML can design professional UIS and animations-Easy to use
• XAML does not require professional programming knowledge. It is easy to understand and has a clear structure-it is easy to learn.
• XAML enables designers to directly participate in software development and communicate at any time without secondary conversion-efficient
However, the talented XAML gentleman is far more than that.
Since the application started from the command line interface (console user interface, Cui, do readers of this book still use dos? After being upgraded to a graphical user interface (GUI), programmers have been pursuing the separation of views (that is, UIS) from logical code. In the past development model, it was difficult for programmers to ensure that the code used to implement the UI is not entangled with the code used to implement the Program Logic. The combination of UI code and logic code is called the tight coupling between UI and logic. It often has the following consequences:
• Changes to software features, UI design, or bugs will lead to a lot of code modifications.
• It makes logical code more difficult to understand-modifications are often more difficult to write because they must be read before modification.
• Reuse logic code into Mission Impossible
Another huge advantage of XAML is that it helps the development team to truly strip the UI and logic. XAML is a pure declarative language. That is to say, it can only be used to declare some UI elements, draw UIS and animations (it is not required to program animations in XAML ), the Program Logic cannot be added to it, which forces the logic code to be removed from the UI code. In this way, all elements related to the UI are concentrated on the UI Layer of the program, and all logic-related code is concentrated on the logic layer of the program, the formation of a "high cohesion-low coupling" structure. After such a structure is formed, it will not take too much effort to make great changes to the ui or to reuse the underlying logic. This is like one day you made an orange for Customer A, and customer a liked it. Customer A introduced your product to Customer B, and customer B liked the orange smell, but hopefully it looks like a banana-at this time, you just need to tear the orange peel down and change it to a set of banana skins-at a very low cost you can get the same benefits as before. (WPF provides a wide range of template functions for the "skin change" behavior of the software, which will be detailed later .)

 

To be continue...