C # design model series Reading Notes ---- Preface
I wrote this C # design model series Reading Notes for a very simple purpose, that is, to take a note of some things I think are more typical in the Process of reading C # design model, serve yourself and others. of course, I have also read the works of some masters in the garden. if anything is wrong, please advise. haha...
First, we all know that there are 23 "design patterns", which are divided into three types.
There are three types of design patterns: creation, structure, and behavior.
The creation mode is to create an object instead of directly instantiating an object, which causes Program It is more flexible when determining which object to create under a given condition.
Structured mode combines a group of objects into a larger structure, such as complex user interfaces or report data.
The behavior mode defines the communication between objects in the system and the process control in complex programs.
Secondly, I think the learning process of the design model
The learning design model requires three phases:
1. Accept.
2. Approval.
3. Understanding.
For acceptance, you need to accept the premise that the design model is very important to your work. Next, you will realize that you need to learn the design model so that you can know when to use the design model. Finally, we need to fully understand the details of the relevant model so that we can know which mode can help us solve the given problems.
For some lucky people, design patterns are obvious tools, and these people only need to read the summary of the patterns to grasp their nature. for most people, there will be a slow perception stage after learning a model, and then they will suddenly realize when they can use these models at work. this series of Reading Notes provides a complete set of programs that can be run and can be tested to help you understand the true meaning of the design model. preface ended. welcome to the discussion. haha. -- note my reference book C # design model, e-Industry Press.