Using the TP, is using CI, feel that they only stay on the use of the framework level. Want to go deeper understanding a framework, have to read CI source code, feel the understanding of CI is still a little help. Want to understand, how to better learn a framework, to understand a framework?
This issue has been turned off because of an issue where the exact result cannot be obtained
Reply content:
Using the TP, is using CI, feel that they only stay on the use of the framework level. Want to go deeper understanding a framework, have to read CI source code, feel the understanding of CI is still a little help. Want to understand, how to better learn a framework, to understand a framework?
I think to understand a framework, it is better to understand the idea of the framework, that is, such as design patterns and other theories, and the framework of the use of the part, can be a good understanding of the framework. Do not directly start each line of code to read directly, so the pattern is too small, it is difficult to promote, should first from the whole to the local, first understand the whole idea, then to the local logic, and finally to the concrete implementation.
We'll use it first.
Then it will change/imitate
At last I will write
What would you do if you were going to write a framework, or a feature? Think well then go to see the framework source code, and you think of the same skip, not the same reflection why, which kind of good.
In addition to do one thing although there are n methods, but the source code has been written must be fixed.
For example, the a approach requires steps a, B, C, and B to take steps 1, 2, 3, 4, 5, if you find that the source code with step B, necessarily represents the corresponding a method, that is to see the whole picture. This recognition method usually look at the function name to know, do not need to see the source code.
As said upstairs, first understand the idea, establish a pre-first understanding, to a certain extent after their own to write a simplified version of the main lean implementation, such as routing, core class loading and so on. The framework covers a wide range of areas and must not be caught