CN113568603B - Component object creating and interface method calling method, terminal and storage device - Google Patents
Component object creating and interface method calling method, terminal and storage device Download PDFInfo
- Publication number
- CN113568603B CN113568603B CN202111116340.7A CN202111116340A CN113568603B CN 113568603 B CN113568603 B CN 113568603B CN 202111116340 A CN202111116340 A CN 202111116340A CN 113568603 B CN113568603 B CN 113568603B
- Authority
- CN
- China
- Prior art keywords
- interface
- component
- acquiring
- information
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
Abstract
The invention provides a method for creating a component object and calling an interface method, a terminal and a storage device, wherein the method comprises the following steps: s101: the component kernel module receives an instruction input by the service module, and executes S102 when the instruction is used for calling a component object to create an interface, or judges whether a preset structural body of the component object is empty or not when the instruction is used for calling a component class method to call the interface, if so, executes S104, and if not, executes S103; s102: searching a component module according to the input component class identifier, and creating a component object through the component module; s103: acquiring component interface information, and storing the component interface information in a preset structure; s104: and calling the interface method by using the interface method attribute information acquired according to the interface method information. The invention realizes the decoupling between the service module and the entity class, reduces the development complexity and the upgrading cost, has strong expandability and greatly reduces the workload and the interaction difficulty.
Description
Technical Field
The invention relates to the field of CAD (computer-aided design), in particular to a component object creating and interface method calling method, a terminal and a storage device.
Background
The dynamic display of entity attribute information in CAD software requires the following steps: the attribute panel displays corresponding attributes according to the selected entity, for example, when a circle is selected, information such as coordinates of a circle center, radius, color, a layer where the circle is located and the like needs to be displayed through an interface, and when another entity such as a straight line is selected, other attributes different from the circle, such as coordinates of a starting point, coordinates of an end point, a line type and the like need to be displayed.
After an entity is selected, a required entity object is directly created according to the objectId (the entity object handle information is recorded) of the selected entity, preset attribute information needing to be displayed is obtained according to the entity type, then the attribute information is traversed, a required entity object method is sequentially called to obtain an attribute value, and the value is filled into a corresponding attribute control to be displayed. However, this approach has the following problems:
the modules are tightly coupled, and programming implementation and upgrading maintenance are difficult. The number of entities in the CAD is large, the number of corresponding entity classes is also large, and because the entity classes need to be created and the attribute values are obtained by calling corresponding methods to display the attribute information, the tight coupling condition between the service module and the entity classes is caused, the realization process is complicated, and the later-stage upgrading and maintenance are difficult;
the support to the self-defined entity is insufficient, and the expansibility is poor. The user self-defines the entities when carrying out secondary development, the entities also need to display the attribute information, because the entity class is not defined by CAD platform software, the attribute information is difficult to be integrated into an attribute panel for display, a special mechanism needs to be established, and the expansibility is poor.
Cross-programming language use is difficult and data interaction is inconvenient. Multiple languages, such as C + +, C, VB, C #, Lisp and the like, are involved in the CAD development process, entity attribute information needs to be acquired among different programming languages for processing, and since the entity class is a C + + language writing module, other programming language modules need to encapsulate and expose class methods when acquiring the entity attribute information, which is complicated to implement.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a component object creating and interface method calling method, a terminal and a storage device, wherein the component object serving as an entity object is created and the interface method is called through a component kernel module, so that decoupling between a service module and an entity class is realized, development complexity and upgrading cost are reduced, the defined component module can be obtained through an identifier, further, the component object is created and the interface method is called, expandability is strong, and the workload and interaction difficulty are greatly reduced.
In order to solve the above problems, the present invention adopts a technical solution as follows: a component object creating and interface method calling method comprises the following steps: s101: the method comprises the steps that a component kernel module receives an instruction input by a service module, S102 is executed when the instruction is used for calling a component object to create an interface, or whether a preset structural body of the component object is empty is judged when the instruction is used for calling a component method to call the interface, if yes, S103 is executed, and if not, S104 is executed; s102: searching a component module according to an input component identifier, acquiring a creating function corresponding to the component identifier in the component module, and creating a component object according to the creating function; s103: acquiring an interface description file corresponding to a component object, acquiring component type interface information corresponding to the component object according to the interface description file, and storing the component type interface information in a preset structure body; s104: and acquiring interface method attribute information from the preset structural body according to the input interface method information, and calling an interface method by using the interface method attribute information, wherein the interface method information comprises an interface method identifier.
Further, the step of searching for a component module according to the input component class identifier specifically includes: reading a registry, and acquiring the component module name corresponding to the component identifier according to the registry, wherein the registry stores the corresponding relation between the component identifier and the component module name.
Further, the step of obtaining the creation function corresponding to the component class identifier in the component module specifically includes: and loading the component module, and acquiring the creating function through a component object creating factory in the component module.
Further, the step of obtaining the creation function according to the component object creation factory in the component module specifically includes: acquiring a handle of the component module, acquiring a component object creation factory from the function according to the address of the creation function derived by the handle acquisition module, and acquiring a creation function corresponding to the component class identifier in the component object creation factory based on the component class identifier.
Further, the step of creating a component object according to the creation function further includes: and calling an interface query function of the component object, and acquiring the interface object of the component object according to the interface identifier of the component class.
Further, the step of obtaining the interface description file corresponding to the component object specifically includes: and acquiring an identifier of the interface description file according to the component object, acquiring the name of the interface description file from a registry according to the identifier, and loading the interface description file corresponding to the name.
Further, the step of obtaining the component class interface information corresponding to the component object according to the interface description file specifically includes: reading the interface description file, acquiring interface description information corresponding to the component interface identifier from the interface description file, and acquiring the component interface information according to the interface description information, wherein the component interface information comprises interface global attribute information and interface method attribute information.
Further, the step of calling the interface method by using the attribute information of the interface method specifically includes: and acquiring a parameter list through the interface method attribute information, acquiring address information of the interface method through the interface method attribute information, and calling the interface method according to the parameter list and the address information.
Based on the same inventive concept, the invention also provides an intelligent terminal, which comprises a service module and a component kernel module, wherein the service module receives an instruction for creating a component object or calling an interface method and sends the instruction to the component kernel module; the component kernel module comprises a component object creating interface and a component class method calling interface, and executes the component object creating and interface method calling method according to the instruction input by the service module.
Based on the same inventive concept, the present invention also provides a storage device storing a computer program for executing the component object creating and interface method calling method as described above.
Compared with the prior art, the invention has the beneficial effects that: the component kernel module is used for creating the component object serving as the entity object and calling the interface method, decoupling between the service module and the entity class is achieved, development complexity and upgrading cost are reduced, the component module defined by the identifier acquisition can be used for creating the component object and calling the interface method, expandability is high, encapsulation and interface exposure are not needed for the entity class, and workload and interaction difficulty are greatly reduced.
Drawings
FIG. 1 is a flow chart of an embodiment of a component object creation and interface method invocation method of the present invention;
FIG. 2 is a diagram illustrating an embodiment of implementation of a component solution in the component object creation and interface method invocation method according to the present invention;
FIG. 3 is a flowchart of one embodiment of component object creation in the component object creation and interface method invocation method of the present invention;
FIG. 4 is a flowchart of an embodiment of component class interface information acquisition in the component object creation and interface method invocation method of the present invention;
FIG. 5 is a flowchart of an embodiment of interface method invocation in the component object creation and interface method invocation methods of the present invention;
FIG. 6 is a block diagram of an embodiment of an intelligent terminal according to the present invention;
FIG. 7 is a block diagram of an embodiment of a memory device according to the invention.
Detailed Description
The present invention will be further described with reference to the accompanying drawings and the detailed description, and it should be noted that any combination of the embodiments or technical features described below can be used to form a new embodiment without conflict.
Referring to fig. 1 to 5, fig. 1 is a flowchart illustrating a method for creating a component object and invoking an interface method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating an embodiment of implementation of a component solution in the component object creation and interface method invocation method according to the present invention; FIG. 3 is a flowchart of one embodiment of component object creation in the component object creation and interface method invocation method of the present invention; FIG. 4 is a flowchart of an embodiment of component class interface information acquisition in the component object creation and interface method invocation method of the present invention; fig. 5 is a flowchart of an embodiment of interface method invocation in the component object creation and interface method invocation methods of the present invention, and details of the component object creation and interface method invocation methods of the present invention are described with reference to fig. 1 to 5.
In this embodiment, the intelligent terminal applying the component object creation and interface method calling method may be a desktop, a notebook, a tablet computer, a server, a cloud platform, or other terminals capable of loading CAD files and creating entity objects.
The intelligent terminal comprises a processor and a memory, wherein the processor is in communication connection with the memory and forms a service module, a component kernel module and a component module according to a computer program in the memory, and the component kernel module is provided with a component object creation interface, a component class object creation factory, a component class method calling interface and an interface description file parser. And the service module loads the component module through the component kernel module to realize the creation of the component object and the calling of the interface method.
In this embodiment, the component object is an entity object, the component module shields implementation details of the component object creation and interface method calling process, and the service module does not need to know implementation details of a class required by the service module and module information where the service module is located, and can implement the service logic of the service module only by interacting with the kernel module.
The component object creation factory includes a map container which records a correspondence between an Identifier (GUID) of a component class and an entry address of a function created by the component class, and a component object acquisition method which can create a corresponding component object according to a specified component class Identifier.
The interface description file parser: the interface description file is an interface description file of the component class, and contains related attribute information of the component class interface, including interface global attribute information (including interface identifier, interface name, inheritance relationship) and interface method attribute information (including interface method name, return value, parameter list, interface method ID, offset address and prompt information).
Component object creation interface: the interface is used for completing the creation of the component object according to the specified component class identifier, and is characterized in that the creation of the required component object can be completed only according to the specified identifier under the condition that the detailed information of the component class and the module where the component class is located are unknown.
Component class method call interface: the component object can call the corresponding interface method by specifying the interface method ID, and at this time, the specific called method name and address information do not need to be known, and only the ID corresponding to the interface method needs to be known, so that the interface realizes the function.
In this embodiment, the method for creating a component object and calling an interface method includes:
s101: the component kernel module receives an instruction input by the service module, and executes S102 when the instruction is to call a component object to create an interface, or judges whether a preset structural body of the component object is empty or not when the instruction is to call a component class method to call the interface, if so, executes S103, and if not, executes S104.
In this embodiment, the service module determines an interface to be called according to the connection requirement, and sends a corresponding interface calling instruction to the component kernel module, and the component kernel module calls the corresponding interface according to the instruction sent by the service module, and feeds back the result to the service module.
The component object creation interface has the main function of creating a specified component object according to the identifier of the component class, and due to the existence of the component kernel, a using module of the component object does not need to know how the component class is created and the implementation details corresponding to the component class, and only needs to call a corresponding function to create the component object according to the component object creation interface, so that the separation of the interface and the implementation is realized, and the coupling degree between the modules is reduced.
Interface method calls can be implemented in two ways: firstly, creating a component object, inputting required parameters, and directly calling a required interface method; and secondly, specifying the name (character string) or ID (identity) of the interface method and parameter information, and realizing interface calling through an intermediate layer, wherein the intermediate layer is written by C + + and is used for constructing various information required by the interface method calling.
S102: searching the component module according to the input component type identifier, acquiring a creating function corresponding to the component type identifier in the component module, and creating a component object according to the creating function.
And after determining that the called interface creates an interface for the component object, creating the component object according to the input component class identifier.
In this embodiment, the step of searching for a component module according to an input component class identifier specifically includes: and reading a registry (storing the corresponding relation between the component identifier and the component module name), and acquiring the component module name corresponding to the component identifier according to the registry, wherein the registry stores the corresponding relation between the component identifier and the component module name.
The step of obtaining the creation function corresponding to the component class identifier in the component module specifically includes: and loading the component module, and acquiring a creating function through a component object creating factory in the component module.
Wherein each component module comprises a component object creation factory, the component object creation factory comprises a map container (the map container is used for recording the corresponding relation between the component class identifier and the component creation function) and a creation function, and the creation function is used for creating the component object and returning the component object.
The step of acquiring the creation function according to the component object creation plant in the component module specifically includes acquiring a handle of the component module, acquiring an address of a component creation function defined in the component module (i.e., a creation function derived from the component module) through the handle, calling the creation function and transferring the component class identifier, and thus, the creation function corresponding to the component class identifier can be acquired from a map container of the component object creation plant.
The step of creating the component object according to the creation function further comprises: and calling an interface query function of the component object, and acquiring the interface object of the component object according to the interface identifier of the component object class.
In a specific embodiment, the component object creation process includes: 1. reading CAD software registry information, and acquiring a corresponding component module name according to a specified component type identifier; 2. if the corresponding component module name is found, loading the component module corresponding to the component module name, initializing a map container (key: component class identifier, value: creating function) in the component module, acquiring a handle of the component module, and acquiring a creating function address derived by the component module through the handle; 3. in the creation function derived by the module, further acquiring a component object creation factory in the component module, traversing map container data in the component object creation factory, and acquiring the creation function corresponding to the component class identifier; 4. if the creating function is successfully acquired, calling the creating function to complete the creation of the component object; 5. and after the component object is established, continuing to call the interface query function of the component object, and acquiring the interface object according to the identifier of the specified interface.
S103: and acquiring an interface description file corresponding to the component object, acquiring component type interface information corresponding to the component object according to the interface description file, and storing the component type interface information in a preset structure body.
In this embodiment, the preset structure is an interface description information structure. The interface description file is an interface description file of the component class, and contains component class interface related information, including interface global attribute information (including interface identifier, interface name, inheritance relationship) and interface method attribute information (including interface method name, return value, parameter list, interface method ID, offset address and prompt information).
In this embodiment, the component kernel module obtains an identifier corresponding to the interface description file through the component object, obtains the name of the interface description file from the registry according to the identifier, and loads the corresponding interface description file according to the name of the interface description file. Wherein the component kernel module further obtains the component class interface identifier from the component object.
The step of obtaining the component class interface information corresponding to the component object according to the interface description file specifically includes: reading the interface description file, acquiring interface description information corresponding to the component interface identifier from the interface description file, and acquiring component interface information according to the interface description information, wherein the component interface information comprises interface global attribute information and interface method attribute information. And acquiring the component interface information by analyzing the interface description information.
In a specific embodiment, the description files are read, the interface description information therein is read and stored one by one, the corresponding interface description information is obtained according to the component interface identifier, wherein one description file may include a plurality of interface description information, each interface description information records the component interface identifier corresponding to itself, when reading, all the interface description information in the interface description files are read into the memory and stored, and then the required specific interface description information is searched from the stored interface description information according to the component interface identifier.
The step of obtaining the component interface information according to the interface description information comprises the following steps: analyzing the interface description information, acquiring global attribute information of the interface, combing the inheritance relationship of the interface, and sequentially reading the interface description information of the inheritance interface according to the acquired inheritance relationship; analyzing from the interface at the uppermost layer of the inheritance relationship to obtain interface method attribute information, wherein the interface method attribute information comprises an interface method ID, an offset address, a function name, a return value, the number and the type of a parameter list; and storing the information into an interface description information structure body, and providing required information for interface method calling.
S104: and acquiring interface method attribute information from a preset structural body according to the input interface method information, and calling an interface method by using the interface method attribute information, wherein the interface method information comprises an interface method identifier.
In other embodiments, the interface method information may also include a name of the interface method and parameter information, and the interface method is called according to the name and the parameter information, wherein the name may be represented in a form of a character string.
Interface method calls can be implemented in two ways: firstly, creating a component object, transmitting required parameters, and directly calling an interface method defined in an interface class; and secondly, specifying the name (character string) or ID (identity) of the interface method and parameter information, and realizing interface calling through an intermediate layer, wherein the intermediate layer is written by C + + and is used for constructing various information required by method calling. The following describes the implementation flow of the second mode.
In this embodiment, before acquiring the interface method attribute information from the preset structure according to the input interface method information, the method further includes: and judging whether the assembly object exists or not and whether the preset structural body is empty or not. If no component object exists, the component object is created based on the specified component class identifier and the component class interface identifier. And if the preset structure of the component object is empty, calling an interface description file parser to generate the preset structure. And if the component object exists and the preset structural body is not empty, acquiring the interface method attribute information from the preset structural body according to the input interface method information.
In this embodiment, the step of acquiring the interface method attribute information from the preset structural body according to the input interface method information includes: traversing a container in the preset structure body, wherein the container records the corresponding relation between the interface method identifier and the interface method attribute information, and acquiring the corresponding interface method attribute information according to the interface method identifier.
In this embodiment, the interface method information further includes a component interface object, an interface method input parameter list, and the interface method identifier includes an interface method ID, an interface class GUID, and other identification information that can be used to identify the interface method attribute information. The interface method attribute information includes information describing the interface method, such as an offset index value, a method name, a parameter list, a return value, and the like.
In this embodiment, after the corresponding interface side attribute information is obtained, it is further required to check whether a parameter list in the interface method attribute information is consistent with an interface side input parameter list (whether the number and the type information in the parameter list are consistent is judged), if so, the next step is executed, and if not, the calling of the interface method is ended.
In this embodiment, the step of calling the interface method by using the attribute information of the interface method specifically includes: and acquiring a parameter list through the interface method attribute information, acquiring address information of the interface method through the interface method attribute information, and calling the interface method according to the parameter list and the address information.
In a specific embodiment, according to the offset address (which is an offset address corresponding to the virtual function table), address information of the interface method is obtained from the virtual function table (class address pointer) of the component class, and the call of the interface method is completed according to the address information and a parameter list in the attribute information of the interface method.
Has the advantages that: the component object creating and interfacing method of the present invention has the following advantages:
1. loose coupling between modules is achieved. The entity object is created by using the component technology, the required entity class can be created by using the component kernel module only by knowing the identifier corresponding to the entity class, the attribute panel module only needs to depend on the component kernel and does not need to depend on the module containing the entity class, the attribute panel module and the module do not depend on each other, decoupling between the modules is realized, and development complexity and later maintenance and upgrading cost are reduced.
2. The expansion and upgrading are more flexible. For the secondary development user-defined entity class, only one component class needs to be defined, and the corresponding relation between the identifier and the component module name is added to the registry, so that the user module is taken as a component module and included in the management range of the component, and the kernel module can complete the creation and calling of the corresponding component class according to the identifier, and has good expandability.
3. And the interaction between different development languages is more convenient. The object creation and the method calling are both realized by the component kernel module, and the entity class module and the specific realization thereof are not needed, so that the interaction between different programming languages does not need to package the entity class and expose the interface, and only the component kernel module creation and calling interface is needed to be exposed, thereby greatly reducing the workload and the interaction difficulty.
Based on the same inventive concept, the present invention further provides a method for creating a component object and invoking an interface method, please refer to fig. 6, and fig. 6 is a structural diagram of an embodiment of an intelligent terminal according to the present invention. The intelligent terminal of the present invention is explained with reference to fig. 6.
In this embodiment, the intelligent terminal includes a service module and a component kernel module, where the service module receives an instruction for creating a component object or calling an interface method, and sends the instruction to the component kernel module; the component kernel module comprises a component object creating interface and a component class method calling interface, and executes the component object creating and interface method calling method according to the instruction input by the service module.
Based on the same inventive concept, the present invention further provides a memory device, please refer to fig. 7, fig. 7 is a structural diagram of an embodiment of the memory device of the present invention, and the memory device of the present invention is described with reference to fig. 7.
In the present embodiment, the storage device stores a computer program used to execute the component object creation and interface method calling method as described in the above embodiments.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (7)
1. A method for creating a component object and calling an interface method is characterized in that the method for creating the component object and calling the interface method comprises the following steps:
s101: the method comprises the steps that a component kernel module receives an instruction input by a service module, S102 is executed when the instruction is used for calling a component object to create an interface, or whether a preset structural body of the component object is empty is judged when the instruction is used for calling a component method to call the interface, if yes, S103 is executed, and if not, S104 is executed;
s102: searching a component module according to an input component class identifier, loading the component module, acquiring a handle of the component module, acquiring an address of a creation function derived by the component module according to the handle, acquiring a component object creation factory in the creation function, acquiring a creation function corresponding to the component class identifier in the component object creation factory based on the component class identifier, and creating a component object according to the creation function, wherein the step of searching the component module according to the input component class identifier specifically comprises:
reading a registry, and acquiring a component module name corresponding to the component identifier according to the registry, wherein the registry stores the corresponding relation between the component identifier and the component module name;
s103: acquiring an interface description file corresponding to a component object, acquiring component type interface information corresponding to the component object according to the interface description file, and storing the component type interface information in a preset structure body;
s104: and acquiring interface method attribute information from the preset structural body according to the input interface method information, and calling an interface method by using the interface method attribute information, wherein the interface method information comprises an interface method identifier.
2. The component object creation and interface method call method of claim 1, wherein the step of creating a component object according to the create function is followed by further comprising:
and calling an interface query function of the component object, and acquiring the interface object of the component object according to the interface identifier of the component class.
3. The method for creating a component object and invoking an interface method according to claim 1, wherein the step of obtaining an interface description file corresponding to a component object specifically comprises:
and acquiring an identifier of the interface description file according to the component object, acquiring the name of the interface description file from a registry according to the identifier, and loading the interface description file corresponding to the name.
4. The method for creating a component object and invoking an interface method according to claim 1, wherein the step of obtaining component class interface information corresponding to a component object according to an interface description file specifically comprises:
reading the interface description file, acquiring interface description information corresponding to the component interface identifier from the interface description file, and acquiring the component interface information according to the interface description information, wherein the component interface information comprises interface global attribute information and interface method attribute information.
5. The method for creating a component object and invoking an interface method according to claim 1, wherein the step of invoking an interface method using the interface method attribute information specifically comprises:
and acquiring a parameter list through the interface method attribute information, acquiring address information of the interface method through the offset address in the interface method attribute information, and calling the interface method according to the parameter list and the address information.
6. An intelligent terminal is characterized in that the intelligent terminal comprises a service module and an assembly kernel module, wherein the service module receives an instruction for creating an assembly object or calling an interface method and sends the instruction to the assembly kernel module;
the component kernel module comprises a component object creation interface and a component class method calling interface, and the component object creation and interface method calling method according to any one of claims 1-5 is executed according to the instruction input by the service module.
7. A storage device storing a computer program for executing the component object creating and interface method calling method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111116340.7A CN113568603B (en) | 2021-09-23 | 2021-09-23 | Component object creating and interface method calling method, terminal and storage device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111116340.7A CN113568603B (en) | 2021-09-23 | 2021-09-23 | Component object creating and interface method calling method, terminal and storage device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113568603A CN113568603A (en) | 2021-10-29 |
| CN113568603B true CN113568603B (en) | 2022-02-15 |
Family
ID=78174088
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111116340.7A Active CN113568603B (en) | 2021-09-23 | 2021-09-23 | Component object creating and interface method calling method, terminal and storage device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113568603B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113989011B (en) * | 2021-12-28 | 2022-04-22 | 深圳华锐分布式技术股份有限公司 | Market data processing method and device, computer equipment and readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1834918A (en) * | 2005-11-04 | 2006-09-20 | 北京金山软件有限公司 | Call method between chip |
| CN108958708A (en) * | 2017-05-25 | 2018-12-07 | 河南理工大学 | A kind of software system architecture component-based and software implementation method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030056194A1 (en) * | 2001-07-16 | 2003-03-20 | Lino Iglesias | Enhanced software components |
| CN112988279A (en) * | 2021-04-16 | 2021-06-18 | 广州南方卫星导航仪器有限公司 | Object processing method and device, electronic equipment and storage medium |
-
2021
- 2021-09-23 CN CN202111116340.7A patent/CN113568603B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1834918A (en) * | 2005-11-04 | 2006-09-20 | 北京金山软件有限公司 | Call method between chip |
| CN108958708A (en) * | 2017-05-25 | 2018-12-07 | 河南理工大学 | A kind of software system architecture component-based and software implementation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113568603A (en) | 2021-10-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9934005B2 (en) | Dynamically building locale objects or subsections of locale objects based on historical data | |
| US6343265B1 (en) | System and method for mapping a design model to a common repository with context preservation | |
| CN111596965B (en) | Project engineering initialization method, device, computer equipment and storage medium | |
| US10635408B2 (en) | Method and apparatus for enabling agile development of services in cloud computing and traditional environments | |
| CN110912724A (en) | Parameter-driven automatic service arrangement method and device | |
| CN113568603B (en) | Component object creating and interface method calling method, terminal and storage device | |
| US20060122958A1 (en) | Matching client interfaces with service interfaces | |
| CN109960709B (en) | Database driver processing method, device, equipment and storage medium | |
| US9141353B2 (en) | Dynamically building locale objects at run-time | |
| US5924100A (en) | Flexible object representation of relational database cells having nontraditional datatypes | |
| CN115269040B (en) | Tenant business application expanding method, device and system | |
| CN114416202B (en) | Mobile terminal SDK calling method and system | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components | |
| CN103677846A (en) | SQLite database development kit and development method thereof | |
| CN112068830A (en) | Avionics system architecture model-oriented design tool | |
| CN111176988B (en) | GoCD-based Python client system | |
| CN114416027A (en) | Software low-code development system and method | |
| TenEyck | Object-Oriented Programming | |
| CN117406985A (en) | Page batch generation method and device | |
| CN117149871A (en) | Multi-source database retrieval method, device, storage medium and computer equipment | |
| CN116795336A (en) | Service interface registration method and device, service interface registration equipment and medium | |
| CN116048999A (en) | Embedded software data access method, device, terminal and storage medium | |
| US9778917B2 (en) | Dynamically building subsections of locale objects at run-time | |
| CN116974562A (en) | List view component packaging method, device and medium based on data binding technology | |
| CN115480792A (en) | System updating method and related equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |