Component concept, someone asks me the concept of the component, I will answer her like this.
If you have any mistakes, everyone will tell me quickly, and quickly correct it, lest her ...
The concept of component concept components is to be generated after an object, is translated vocabulary. In fact, the components are objects. Chinese people like smart, they will find N vocabulary to express it. So in C Builder, it is a component. In Delphi, it is called a component, and it is called a control in VB, returning to the object-oriented object, also known as classes and objects. So, our Chinese nouns are turning down, it is a matter. Now I will tell you carefully. There is a group of methods, the operation of the method requires a set of data, and makes them into packages, turning into components. Will you say this is the same as the class? Nothing is not. The class is existing in the form of the source code, and the component is the result of the encapsulation with the binary executable code. In the object-oriented language, the components are generally derived from xxcomponent. The XX here is different from the language, which is a word. As components and classes, there are properties and methods. Components are visualized, and non-visual. Visual components can see them like they like the VB controls, Delphi components, and they can see them, and can also manually modify their properties during design. From the perspective of the user (Application Developer), the component is already written, the third-party program that tests is not problematic, but it is only used. Of course, you can also develop components. From the actual form, the components are different depending on the standard, and Delphi, CB is the BPL format, and VB is OCX format, and the VC is reached, and the VC # becomes COM format. In fact, .NET is also a COM format. Ha ha. Of course there are other formats. Specifically, the components of each family have their own points, realization (development) is different. But one thing is the same, that is, anyone can develop components, just follow it standard (format). In general, development component work is more heavy and requires a relatively high requirements. The most important thing is because the developed components are used for others. Since it is to use it, the quality is going to pass, it is necessary to have less mistakes, try not to do BUG. The development component process is generally as follows: 1. Using the IDE to generate a component frame (of course, you can also do it manually, I am not tired, I am not responsible) 2. According to the need to increase your own method and attribute 3, respond to the change of attribute modification and write method code 4. Some components have an event saying that 5, compile 6, write one component user to debug component 7, using write components, methods, events.
Here is the design of the component development needs to be done. It is the layout of component functions. In fact, there is nothing to say, just press the object-oriented idea, you can do it according to the design idea (object-oriented).
