组件和控件（国外英文资料）.docVIP

组件和控件（国外英文资料） Normally, Control is translated into a Control, and Component is translated into components. A control is a component that has a user interface. Early to say specific point, you have to review the historical roots of the Windows, then control refers to any child window, buttons, list box, edit box, or static text in a dialog box. Conceptually, these Windows -- controls -- are similar to the knobs and buttons used to operate a radio or gadget. With an increase in the number of controls, combo box, date, time controls, etc.), become the pronoun of child window controls gradually, whether in the dialog box or use in other kinds of the main window. It wasnt long before BASIC programmers began to write their own special controls, and naturally people wanted to share them. One way to share code is to copy it from disk, but thats obviously inefficient. There must be a mechanism enables developers to build controls easily inserted in the application of other programmers, this is the VBA controls, OLE controls, OCX and finally the motives of ActiveX controls. This is where the confusion arises between the control and the component. Because in order to solve the reusable problems of controls, all of these technologies must first address the more general issues of component reuse. (COM, if you remember it, it means the component object model). In software lingo, the term component refers to any reusable object or any code that interacts with other objects. The invention of the subroutine, once become programmers have the holy grail of software engineering: a unified theory of programming, it makes the programmer from the basic building blocks - that is, written in the selected language of various components to build larger systems. From a subroutine to OOP, to DLLs, to COM, and to the.net framework, every new paradigm of programming represents a different approach to providing reusability. VBX USES the solidified name of DLLs. COM USES interfaces and IUnknown. T