CN107479867B - Application software plug-in operation method and device - Google Patents
Application software plug-in operation method and device Download PDFInfo
- Publication number
- CN107479867B CN107479867B CN201710439479.2A CN201710439479A CN107479867B CN 107479867 B CN107479867 B CN 107479867B CN 201710439479 A CN201710439479 A CN 201710439479A CN 107479867 B CN107479867 B CN 107479867B
- Authority
- CN
- China
- Prior art keywords
- plug
- interaction unit
- application software
- software
- unit
- 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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a device for the plug-in operation of application software, wherein the method comprises the following steps: configuring a first plug-in interaction unit in application software to form a plug-in; installing the plug-in the host software configured with the second plug-in interaction unit; the first plug-in interaction unit is matched with the second plug-in interaction unit; the host software loads and calls the component information of each functional module in the application software through the second plug-in interaction unit and the first plug-in interaction unit; and the functional module calls the data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit to execute the logic function. The invention realizes that a plurality of sets of codes are not required to be developed and maintained synchronously by configuring the matched plug-in interaction units in the application software and the host software respectively and taking the application software as the plug-in of the host software to be installed and operated, thereby greatly reducing the development cost and the synchronous maintenance cost of a software developer.
Description
Technical Field
The application relates to the technical field of application software, in particular to a method and a device for plug-in operation of application software.
Background
Under the large environment of mobile internet and intelligent terminal, the application environment, type, path, purpose, etc. of different devices are different. Each user often uses different terminal devices or application software, and different channel path methods may exist in a specific environment, so that an application software developer has to spend more manpower, material resources, financial resources and the like to popularize and operate and maintain different channels, versions, OEMs and other special applications, and further great synchronous maintenance cost is brought to the application software developer. Meanwhile, the applications of different channels, paths and versions are often not converged in time, and further, functional activities such as specific business operation revenue change and the like cannot be effectively and uniformly performed on all the channels and the path versions, so that the function popularization and the business cooperation change of the whole activities are seriously influenced, and the actual use effect experience and the product image brand awareness of specific users are further influenced.
Disclosure of Invention
In view of the above-mentioned drawbacks and deficiencies in the prior art, it is desirable to provide a method and an apparatus for plug-in operation of application software, which can be applied to different system environments by only developing and maintaining a set of codes for an application program.
In a first aspect, the present invention provides a method for plug-in running of application software, the method including:
configuring a first plug-in interaction unit in application software to form a plug-in;
installing the plug-in the host software configured with the second plug-in interaction unit; the first plug-in interaction unit is matched with the second plug-in interaction unit;
the host software loads and calls the component information of each functional module in the application software through the second plug-in interaction unit and the first plug-in interaction unit;
and the functional module calls the data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit to execute the logic function.
In a second aspect, the invention provides an application software plug-in running device, and the system comprises a plug-in unit and a running environment configuration unit.
The plug-in unit is used for configuring a first plug-in interaction unit in the application software to form a plug-in;
and the running environment configuration unit is used for installing the plug-in the host software configured with the second plug-in interaction unit so that the host software loads and calls the component information of each functional module in the application software through the second plug-in interaction unit and the first plug-in interaction unit, and the functional module calls the data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit so as to execute the logic function.
The first plug-in interaction unit is matched with the second plug-in interaction unit.
In a third aspect, the present invention also provides an apparatus comprising one or more processors and a memory, wherein the memory contains instructions executable by the one or more processors to cause the one or more processors to perform the application software plug-in execution method provided according to the embodiments of the present invention.
In a fourth aspect, the present invention further provides a computer-readable storage medium storing a computer program, where the computer program makes a computer execute the application software plug-in operation method provided in accordance with the embodiments of the present invention.
According to the method and the device for the application software plugin operation, which are provided by the embodiments of the invention, the application software is used as the plugin of the host software to be installed and operated by respectively configuring the matched plugin interaction units in the application software and the host software, so that one application program can be applied to different system environments by only developing and maintaining one set of codes without developing and synchronously maintaining a plurality of sets of codes, and the development cost and the synchronous maintenance cost of a software developer are greatly reduced;
the method and the device for the application software plug-in operation provided by some embodiments of the invention further adopt a method of packaging a self-defined interface file, adding the interface file during compiling, and quoting the data information of a corresponding file class in the host software without adding the interface file during packaging, so that the plug-in can directly multiplex the latest code logic of the host software during running while ensuring the normal execution of code compiling, thereby only paying attention to the interface method in the process of plug-in development (the configuration of a first plug-in interaction unit) without paying attention to the logic entity of the host software, and further realizing the independent development and online support dependence of the host software and the plug-in;
the method and the device for the application software plug-in operation provided by some embodiments of the invention further realize that the application software converted into the plug-in is operated as an independent application by configuring an independent operation module in the interface file, thereby meeting the requirement of flexibly configuring a use mode;
the method and the device for the application software plug-in operation provided by some embodiments of the invention further improve the compatibility of the plug-ins by configuring the first plug-in interaction unit to be matched with each second plug-in interaction unit respectively configured in each host software in different platform systems;
the method and the device for the application software plug-in operation provided by some embodiments of the present invention further implement configuring personalized customization functions for different platform systems by adding a function customization subunit in the first plug-in interaction unit, so as to meet different requirements of each platform channel.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a flowchart of an application software plug-in operation method according to an embodiment of the present invention.
FIG. 2 is a schematic diagram of application software pluggability in the method shown in FIG. 1.
FIG. 3 is a flow diagram of a preferred embodiment of the method shown in FIG. 1.
Fig. 4 is a schematic structural diagram of an application software plug-in operating device according to an embodiment of the present invention.
Fig. 5 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 is a flowchart of an application software plug-in operation method according to an embodiment of the present invention.
As shown in fig. 1, in this embodiment, the method for running an application software in a plug-in mode provided by the present invention includes:
s10: configuring a first plug-in interaction unit in application software to form a plug-in;
s30: installing the plug-in the host software configured with the second plug-in interaction unit; the first plug-in interaction unit is matched with the second plug-in interaction unit;
s50: the host software loads and calls the component information of each functional module in the application software through the second plug-in interaction unit and the first plug-in interaction unit;
s70: and the functional module calls the data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit to execute the logic function.
The above steps will be described in detail by taking as an example that the traffic management application software is inserted and installed in the search engine software as host software to be run.
FIG. 2 is a schematic diagram of application software pluggability in the method shown in FIG. 1. As shown in fig. 2, in step S10, the traffic management application software itself includes a setting management unit, a traffic calibration unit, a traffic monitoring unit, and a data update unit, and a first plug-in interaction unit with a light configuration weight is introduced into the software, so as to form a traffic management plug-in together with the original four functional units.
Specifically, the first plug-in interaction unit comprises a function interaction subunit and a data interaction subunit.
The function interaction subunit comprises a plug-in monitoring function calling module, a plug-in calibration function calling module, a plug-in function updating notification module and the like. The plug-in monitoring function calling module is used for enabling host software (through a second plug-in interaction unit) to call various component information of a flow monitoring unit of the flow management plug-in, such as a monitoring interface and the like; the plug-in calibration function calling module is used for the host software (through the second plug-in interaction unit) to call various component information of the flow calibration unit of the flow management plug-in; the plug-in function update notification module is used for notifying the host software of the traffic management plug-in when a new function event occurs (through the second plug-in interaction unit).
The data interaction subunit comprises a plug-in data query module, a plug-in data update notification module, a functional instruction data interaction module and the like. The plug-in data query module is used for host software (through a second plug-in interaction unit) to query data of the flow management plug-in; the plug-in data updating notification module is used for notifying the flow management plug-in to host software (through a second plug-in interaction unit) when data is updated; the functional instruction data interaction module is used for being matched with the second plug-in interaction unit for the traffic management plug-in and the host software to carry out interaction sending of functional instructions.
In the above, the first plug-in interaction unit cooperating with the traffic management application software is taken as an example, and the subunits and the specific modules included in the first plug-in interaction unit are listed, but the first plug-in interaction unit provided in this embodiment and the present invention is not limited thereto, and for the first plug-in interaction unit cooperating with different application software, different subunits and specific modules may be configured according to actual requirements, as long as the first plug-in interaction unit can cooperate with the second plug-in interaction unit configured in the host software to meet the requirements of functional interaction and data interaction between the application software and the host software, and the same technical effect can be achieved.
More specifically, in a preferred embodiment, the first plug-in interaction unit matches only the second plug-in interaction unit of the host software configuration in the current platform system. For example, for the host software installed in the android system, a second plug-in interaction unit (android version) is configured; configuring a second plug-in interaction unit (IOS version) for host software installed in the IOS system; for the host software installed in the WINDOWS system, a second plug-in interactive element (WINDOWS version) is configured, and so on. Therefore, for application software needing to be installed in the android system in a plug-in mode, only subunits and modules matched with a second plug-in interaction unit (android version) are configured in the first plug-in interaction unit; for application software needing to be installed in an IOS system in a plug-in mode, only sub-units and modules matched with second plug-in interaction units (IOS versions) are configured in the first plug-in interaction unit; and so on. In this embodiment, for different platform systems, different versions of the first plug-in interaction unit need to be configured for the application program, and the data lightweight of the first plug-in interaction unit can be further ensured.
In another preferred embodiment, the first plug-in interaction unit is matched with each second plug-in interaction unit respectively configured in each host software in different platform systems. That is, the first plug-in interaction unit includes all sub-units and modules matching with the second plug-in interaction unit of different version. In this embodiment, the plug-in generated in step S10 may be installed in host software of any platform system, so that compatibility of the plug-in is greatly improved, and different first plug-in interaction units do not need to be configured for different platform systems separately, and plug-ins of different versions do not need to be selected according to different platform systems.
In step S30, the traffic management plug-in generated in step S10 is installed in search engine software as host software. And a second plug-in interaction unit matched with the first plug-in interaction unit is configured in the search engine software.
Specifically, in this embodiment, the second plug-in interaction unit configured in the search engine software is not only matched with the first plug-in interaction unit in the traffic management plug-in, but also matched with the first plug-in interaction units in a plurality of different plug-ins, such as the power management plug-in, the translation plug-in, and the like, so that the search engine software can install not only the traffic management plug-in, but also a plurality of different plug-ins, such as the power management plug-in, the translation plug-in, and the like.
In more embodiments, the second plug-in interaction unit may also be configured to match with the first plug-in interaction unit configured in one or a few plug-ins according to different actual requirements such as security.
In step S50, the search engine software loads and calls the component information of each function module in the traffic management application software through the second plug-in interaction unit and the first plug-in interaction unit configured in the traffic management plug-in.
Specifically, the existing plug-in scheme is basically implemented by the inheritance of the main body type and the reloading of the functional logic of the parent class of the corresponding class file, so that the plug-in corresponding to the application software needs to forcibly carry out the inheritance of the type and the reloading processing different from those of basic components such as the default Android and the like when the code is written, so that the plug-in cannot be directly constructed to operate under the condition that the original independently operated application software does not modify the code, and further the function and data interaction between the host software and the plug-in cannot be further realized.
In the solution of this embodiment, taking an Android system as an example, when a traffic management plug-in is loaded and run for the first time, component information is loaded and called in at least one of the following ways, so that the plug-in can be configured to run without modifying a code of traffic management application software:
a first plug-in interaction unit configured in the flow management plug-in dynamically loads Proxy classes of core component classes such as Activity, Service, Broadcast Receiver, Content Provider and the like in the Android Framework of the current platform system through a second plug-in interaction unit configured in search engine software;
and dynamically injecting a system interface method for replacing the current platform system by a first plug-in interaction unit configured in the flow management plug-in through a second plug-in interaction unit configured in search engine software.
In step S70, the traffic management plug-in calls data information to the search engine software through the first plug-in interaction unit and the second plug-in interaction unit to perform a logical function.
Specifically, data exchange can be performed between the first plug-in interaction unit and the second plug-in interaction unit through any one or more of the following manners: global sharing, file sharing, Android interface definition language (AIDL for short), Binder and other cross-process calling modes.
In a preferred embodiment, the first plug-in interaction unit may also quickly call the data information of the host software to the second plug-in interaction unit by: and packaging the self-defined interface file, adding the interface file during compiling, and referring to the corresponding file class in the host software without adding the interface file during packaging.
Specifically, by the quick calling mode, normal execution of code compiling is guaranteed, and meanwhile, the plug-in can directly reuse the latest code logic of the host software during running, so that only an interface method needs to be concerned in the plug-in development process (configuration of the first plug-in interaction unit), and the logic entity of the host software does not need to be concerned, and independent development and online support dependence of the host software and the plug-in are realized.
Furthermore, a fault-tolerant processing module can be configured in the interface file to provide a fault-tolerant processing function; and configuring an independent operation module in the interface file to provide a function of operating the application software as an independent application, so that the requirement of flexibly configuring a use mode is met.
In the embodiment, the application software is used as the plug-in of the host software to be installed and operated by respectively configuring the matched plug-in interaction units in the application software and the host software, so that one application program can be applied to different system environments only by developing and maintaining one set of codes without developing and synchronously maintaining a plurality of sets of codes, and the development cost and the synchronous maintenance cost of a software developer are greatly reduced.
FIG. 3 is a flow diagram of a preferred embodiment of the method shown in FIG. 1.
As shown in fig. 3, in a preferred embodiment, step S30 is preceded by:
s20: and adding a function customizing subunit in the first plug-in interaction unit for customizing the functions configured for the current platform system.
Specifically, different platform channels often have different user requirements, or different activities need to be arranged, and the like, and at this time, modifying the application software code causes synchronous change of plug-ins installed in all platform systems, which makes it difficult to meet the requirements. By adding the function customizing subunit in the first plug-in interaction unit of the plug-in, the functions required by the current platform channel can be customized in the respective plug-ins respectively so as to meet the requirements.
The above embodiment further realizes configuring personalized customization functions for different platform systems by adding the function customization subunit in the first plug-in interaction unit, so as to meet different requirements of each platform channel.
Fig. 4 is a schematic structural diagram of an application software plug-in operating device according to an embodiment of the present invention. The device shown in fig. 4 can correspondingly execute the method provided by any of the above embodiments.
As shown in fig. 4, in the present embodiment, the present invention provides an application software plug-in running device 10, which includes a plug-in unit 11 and a running environment configuration unit 13.
The plug-in unit 11 is configured to configure a first plug-in interaction unit in the application software to constitute a plug-in;
the runtime environment configuration unit 13 is configured to install the plug-in generated by the plug-in unit 11 in the host software installed in the mobile device 20 and configured with the second plug-in interaction unit, so that the host software loads and calls the component information of each function module in the application software through the second plug-in interaction unit and the first plug-in interaction unit, and the function module of the plug-in calls the data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit to execute the logic function.
The first plug-in interaction unit is matched with the second plug-in interaction unit.
The principle of the plug-in operation of the application software refers to the method embodiments shown in fig. 1 to 3, and is not described herein again.
Fig. 5 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
As shown in fig. 5, as another aspect, the present application also provides an apparatus including one or more Central Processing Units (CPUs) 501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM503, various programs and data necessary for the operation of the apparatus 500 are also stored. The CPU501, ROM502, and RAM503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to an embodiment of the present disclosure, the application software plug-in operation method described in any of the above embodiments may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing a method for plug-in execution of application software. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511.
As yet another aspect, the present application also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the apparatus of the above-described embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer readable storage medium stores one or more programs for use by one or more processors in performing the application plug-in execution methods described herein.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, for example, each of the described units may be a software program provided in a computer or a mobile intelligent device, or may be a separately configured hardware device. Wherein the designation of a unit or module does not in some way constitute a limitation of the unit or module itself.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the present application. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. An application software plug-in operation method is characterized by comprising the following steps:
configuring a first plug-in interaction unit in application software to form a plug-in;
installing the plug-in host software configured with a second plug-in interaction unit; the first plug-in interaction unit is matched with the second plug-in interaction unit;
the host software loads and calls the component information of each functional module in the application software through the second plug-in interaction unit and the first plug-in interaction unit;
the functional module calls data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit to execute a logic function;
the loading and calling are realized by at least one of the following modes:
the first plug-in interaction unit dynamically loads the proxy class of the core component class of the current platform system through the second plug-in interaction unit;
and the first plug-in interaction unit dynamically injects a system interface method for replacing the current platform system through the second plug-in interaction unit.
2. The method for plug-in operation of application software according to claim 1, wherein the first plug-in interaction unit and the second plug-in interaction unit exchange data with each other by at least one of the following methods: global sharing, file sharing, cross-process calling.
3. The method for the plugin operation of application software according to claim 1, wherein the first plugin interactive unit quickly calls data information of host software to the second plugin interactive unit by: and packaging the self-defined interface file, adding the interface file during compiling, and referring to the corresponding file class in the host software without adding the interface file during packaging.
4. The method for the plugin operation of application software according to claim 3, further comprising at least one of:
configuring a fault-tolerant processing module in the interface file to provide a fault-tolerant processing function;
and configuring an independent operation module in the interface file to provide the function of operating the application software as an independent application.
5. The method for the plug-in operation of the application software according to any one of claims 1 to 4, further comprising:
and adding a function customizing subunit in the first plug-in interaction unit for customizing the function configured for the current platform system.
6. The method for plugin operation of application software according to any of claims 1 to 4, wherein the first plugin interactive unit is matched with each second plugin interactive unit respectively configured in each host software in different platform systems.
7. The method for plug-in operation of application software according to any one of claims 1 to 4, wherein the second plug-in interaction unit is matched with each first plug-in interaction unit configured in each different plug-in.
8. An application software plug-in running device, comprising:
the plug-in unit is configured for configuring a first plug-in interaction unit in the application software to form a plug-in;
the running environment configuration unit is configured to install the plug-in the host software configured with the second plug-in interaction unit, so that the host software loads and calls component information of each functional module in the application software through the second plug-in interaction unit and the first plug-in interaction unit, and the functional module calls data information to the host software through the first plug-in interaction unit and the second plug-in interaction unit to execute a logic function;
the first plug-in interaction unit is matched with the second plug-in interaction unit;
the loading and calling are realized by at least one of the following modes:
the first plug-in interaction unit dynamically loads the proxy class of the core component class of the current platform system through the second plug-in interaction unit;
and the first plug-in interaction unit dynamically injects a system interface method for replacing the current platform system through the second plug-in interaction unit.
9. An apparatus, characterized in that the apparatus comprises:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method recited in any of claims 1-7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710439479.2A CN107479867B (en) | 2017-06-12 | 2017-06-12 | Application software plug-in operation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710439479.2A CN107479867B (en) | 2017-06-12 | 2017-06-12 | Application software plug-in operation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107479867A CN107479867A (en) | 2017-12-15 |
| CN107479867B true CN107479867B (en) | 2020-12-18 |
Family
ID=60593971
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710439479.2A Active CN107479867B (en) | 2017-06-12 | 2017-06-12 | Application software plug-in operation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107479867B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108595203B (en) * | 2018-04-28 | 2024-04-19 | 努比亚技术有限公司 | Application function execution method, mobile terminal and computer readable storage medium |
| CN109582342A (en) * | 2018-11-29 | 2019-04-05 | 珠海豹趣科技有限公司 | A kind of processing method and relevant apparatus of OEM software |
| CN109683945A (en) * | 2018-12-12 | 2019-04-26 | 泰康保险集团股份有限公司 | Routine interface processing method and system, its computer-readable medium and electronic equipment |
| CN111399927B (en) * | 2018-12-14 | 2024-06-18 | 北京奇虎科技有限公司 | Method and device for sharing Class files by application and computing equipment |
| CN109725952B (en) * | 2019-01-07 | 2021-09-24 | 深圳市网心科技有限公司 | Method, system and related device for application program plug-in |
| CN110096282A (en) * | 2019-05-15 | 2019-08-06 | 湖南快乐阳光互动娱乐传媒有限公司 | Data processing method and device based on plug-in architecture |
| CN110221877B (en) * | 2019-06-12 | 2022-06-07 | 北京字节跳动网络技术有限公司 | Application program running method and device, electronic equipment and storage medium |
| CN110297644A (en) * | 2019-06-24 | 2019-10-01 | 深圳市酷开网络科技有限公司 | A kind of homepage, which suspends, applies setting method, intelligent terminal and storage medium |
| CN110515673B (en) * | 2019-07-24 | 2022-10-11 | 百度在线网络技术（北京）有限公司 | Plug-in system and method thereof |
| CN113625997B (en) * | 2021-07-20 | 2024-03-12 | 青岛小鸟看看科技有限公司 | XR software development architecture, application method and electronic equipment |
| CN114064322A (en) * | 2021-11-23 | 2022-02-18 | 上海同星智能科技有限公司 | Software host construction method, construction system, software host and simulation equipment |
| CN114461295A (en) * | 2021-12-27 | 2022-05-10 | 上海交通大学四川研究院 | Method, device, equipment and medium for generating software system based on plug-in sharing |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101699405B (en) * | 2009-10-26 | 2014-06-11 | 中兴通讯股份有限公司 | Method and device for interaction between host program and plug-in and interaction between plug-ins |
| CN105653335A (en) * | 2015-12-31 | 2016-06-08 | 北京锐安科技有限公司 | Plug-in procedure control method and device |
-
2017
- 2017-06-12 CN CN201710439479.2A patent/CN107479867B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107479867A (en) | 2017-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107479867B (en) | Application software plug-in operation method and device | |
| US10740114B2 (en) | Component invoking method and apparatus, and component data processing method and apparatus | |
| US11966795B2 (en) | Method and device for loading minus-one screen, terminal, and computer readable storage medium | |
| CN104834541B (en) | Function module hanging method, carry system and the method for updating carry system | |
| CN110442327B (en) | Application program construction method, device and server | |
| CN111182019B (en) | Cross-platform communication method and device and electronic equipment | |
| CN112416415A (en) | Front-end micro-service implementation method and related components | |
| CN106953746A (en) | Clustered node upgrade-system and method | |
| CN103530097B (en) | The implementation method and device of a kind of component across middleware platform | |
| CN108021377A (en) | A kind of application icon update method and device | |
| CN104239114A (en) | Application compiling method and device | |
| US20100293201A1 (en) | Nfs agent upgrade | |
| CN112000353A (en) | Application running method and device and storage medium | |
| CN113468067B (en) | Application program debugging method and device, electronic equipment and computer readable medium | |
| CN114996337A (en) | Multi-cluster database management system and method | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN113191889A (en) | Wind control configuration method, configuration system, electronic device and readable storage medium | |
| CN110599112B (en) | Network page development and maintenance method and device | |
| CN106033364B (en) | Web application program upgrading method and system | |
| US10686717B1 (en) | Dynamic allocation of content requests to content providers | |
| CN113434233B (en) | Interface jump method and device, storage medium and electronic device | |
| CN114579167B (en) | Method, device and storage medium for downloading application upgrade file | |
| CN113448585B (en) | Compiling method and device of thread pool, electronic equipment and storage medium | |
| CN115129348A (en) | Resource updating method, device and equipment of application program and readable storage medium | |
| CN113050962B (en) | Mobile service upgrading method, device and terminal |
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 |