Design mode-appearance (facade) mode

Insus.net wrote a "software development company, design pattern (facade)" Last year http://www.cnblogs.com/insus/archive/2013/02/27/2936061.html The example is too simple and abstract to write. No substance.

I want to write another one this time. Hope to be strengthened again. providing a unified high-level interface to a set of interfaces in a subsystem makes it easier for customers to use subsystems This is the essence of the appearance (facade) pattern.

Before you do this, you can look at the function of the Web control text box reset http://www.cnblogs.com/insus/p/4123239.html, which is the function that requires each control to reset. Although Insus.net uses several custom classes (adapter), this custom class implements an interface (interface). The controls that need reset are then added to a set to complete their respective reset functions.

In fact, in this case, it is very well suited to use the appearance (facade) pattern to implement.



This way, we can rewrite it in the program:

Dynamic Live Demo:



The source program can be downloaded from the following link:
Http://download.cnblogs.com/insus/CSharpNET/Facade_Pattern_control_reset.rar

Design mode-appearance (facade) mode