WO2020135129A1 - Method and device for loading plug-in of application, and terminal - Google Patents

Abstract

A method and device for loading a plug-in of an application, and a terminal, relating to the field of computers. The method may comprise: receiving an instruction for triggering the loading of a plug-in (110); obtaining configuration information of the plug-in, the configuration information being generated based on loading settings of the plug-in on a plug-in configuration interface, and the plug-in configuration interface being an interface for configuring all plug-ins of the application (120); and loading the plug-in according to the configuration information (130).

Description

Method, device and terminal for loading application plug-in

cross reference

The present invention requires the priority of the Chinese patent application filed on December 25, 2018 in the Chinese Patent Office with the application number 201811595293.7 and the invention titled "Method, Device and Terminal for Loading Application Plug-ins". The entire content of this application is cited by reference Incorporated in the invention.

Technical field

The invention relates to the field of computers, and in particular to a method, device and terminal for loading application plug-ins.

Background technique

With the popularity of smart phones and the increasingly powerful application functions, plug-in-based development methods are currently introduced for some large-scale applications.

The plug-in-based development method is favored by the majority of users because of its ease of management and the need to reinstall the plug-in installation package during upgrade.

In the related art, the same loading method is used when loading different plug-ins of the same application program, and the flexibility of this loading method is poor.

Summary of the invention

Embodiments of the present application provide a method, device, and terminal for loading application plug-ins to solve the problem of poor flexibility caused by the same loading method when loading different plug-ins of the same application program in the related art .

In a first aspect, an embodiment of the present application provides a method for loading a plug-in of an application, including: receiving an instruction that triggers the loading of a plug-in; acquiring configuration information of the plug-in, the configuration information is based on the configuration of the plug-in configuration interface Generated by loading settings of the plug-in, the plug-in configuration interface is an interface for configuring all plug-ins of the application; according to the configuration information, the plug-in is loaded.

In a second aspect, an embodiment of the present application provides an apparatus for loading a plug-in for an application, including: a receiving module for receiving an instruction that triggers the loading of a plug-in; an acquiring module for acquiring configuration information of the plug-in, the configuration information It is generated based on the loading settings of the plug-in on the plug-in configuration interface. The plug-in configuration interface is an interface for configuring all plug-ins of the application; a loading module is used to obtain the configuration according to the acquisition module Information to load the plug-in.

In a third aspect, an embodiment of the present application provides a terminal, including: a memory and a processor, a computer program is stored on the memory, and when the computer program is executed, the plug-in for loading an application described in the first aspect is implemented Steps in the method.

According to a fourth aspect, an embodiment of the present application provides a non-transitory computer-readable storage medium that stores a computer program, and when the computer program is executed, implements the method for loading an application plug-in described in the first aspect Steps.

BRIEF DESCRIPTION

In order to more clearly explain the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only These are the embodiments described in the present invention. For those of ordinary skill in the art, without paying any creative labor, other drawings can also be obtained based on these drawings.

1 is a flowchart of a method for loading an application plug-in provided by an embodiment of the present invention;

2 is a flowchart of another method for loading an application plug-in provided by an embodiment of the present invention;

3 is a structural block diagram of an apparatus for loading an application plug-in provided by an embodiment of the present invention;

4 is a schematic structural diagram of a terminal provided by an embodiment of the present invention.

detailed description

In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be described clearly and completely in conjunction with the drawings in the embodiments of the present invention. Obviously, the described The embodiments are only a part of the embodiments of the present invention, but not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

In the embodiments of the present invention, it should be understood that an application means an application program.

It should be understood that in the following description, if the Android system is mentioned, it only means that the Android system is used as an example for illustration, not limitation, and the method for loading an application plug-in provided by an embodiment of the present invention can also be applied to other operating systems. , Such as Apple's operating system (iOS).

In the embodiment of the present invention, the plug-in is a program written by an application program interface that complies with certain specifications, and can only be run under the system platform specified by the program, and cannot be run separately from the specified platform. In other words, the plug-in can provide a dynamic expansion capability, so that the application program loads the functions that are not originally part of the application at runtime, and can be dynamically updated and replaced.

In Android, plug-in development is to encapsulate some core complex and highly dependent business modules into independent plug-ins, and then combine them according to different business needs, dynamically replace them, and manage and update the plug-ins. The plugin can also perform version management and other operations.

The technical solutions provided by the embodiments of the present invention will be described in detail below in conjunction with the drawings.

The method of loading an application plug-in provided by an embodiment of the present invention will be described below from the perspective of a terminal. Wherein, the terminal may be a mobile phone, a tablet computer or the like. FIG. 1 is a flowchart of a method for loading an application plug-in provided by an embodiment of the present invention. Referring to FIG. 1, a flowchart of a method for loading an application plug-in provided by an embodiment of the present invention may include the following steps.

Step 110: Receive an instruction that triggers plugin loading.

In the embodiment of the present invention, when a user clicks on a plug-in of an application (such as WeChat, etc.) installed on the terminal, for example, an instruction that triggers the loading of the plug-in may be received. Taking WeChat as an example, the plug-ins on WeChat may include multiple plug-ins located in "I"-"My Wallet"-"Third Party Service". When the user clicks on one of the plug-ins, the terminal can receive an instruction that triggers the loading of the plug-in.

After step 110, the terminal can perform the following dynamic loading process: copy the executable file of the plug-in (.so/dex/jar/apk, etc.) to the inside of the application; load the executable file and replace the static resource; call a specific method Perform business logic.

The method for loading an application plug-in provided by an embodiment of the present invention is mainly to improve the process of loading an executable file and replacing static resources. Among them, the static resource may be a resource that the plug-in may be called during the running process. Static resources may for example involve pictures of plug-ins and/or pre-compiled libraries, etc.

Step 120: Obtain configuration information of the plug-in. The configuration information is generated based on loading settings of the plug-in on the plug-in configuration interface. The plug-in configuration interface is an interface for configuring all plug-ins of the application.

Among them, step 120 may be executed during the loading of the executable file.

In the embodiment of the present invention, the plug-in configuration interface may also only cover the configuration of the loaded plug-in. The plugin configuration interface may include various loading options, such as loading method options.

In the embodiment of the present invention, the configuration information of the plug-in can be obtained in various ways. For example, when the plug-in is started for the first time, it may be confirmed whether the user has configured the plug-in through the plug-in configuration interface before the plug-in is started. If the user does not configure the plug-in through the plug-in configuration interface before the plug-in is started, the configuration information of the plug-in can be obtained by default; if the user configures the plug-in through the plug-in configuration interface before the plug-in is started, the user can select from Obtain loading settings for the plug-in through the plug-in configuration interface at a designated location.

In the embodiment of the present invention, if the user configures the plug-in through the plug-in configuration interface before the plug-in starts, the plug-in can be set through the plug-in configuration interface, and the obtained load settings (the first load Settings) are stored in designated locations for subsequent access. After obtaining the configuration information of the plug-in in step 110, the configuration information of the plug-in may be written into an extensible markup language (eXtensible Markup Language, XML) configuration file in the terminal. In the embodiment of the present invention, an XML configuration file may be used to store configuration information of all plug-ins on the terminal. Subsequently, the configuration information of the corresponding plug-in can be obtained by reading the XML configuration file.

When the plug-in is not started for the first time, it can read the XML configuration file in the terminal; and obtain the configuration information of the plug-in from the XML configuration file.

Step 130: Load the plug-in according to the configuration information.

In this embodiment of the present invention, the configuration information may include a first loading mode and a second loading mode. The first loading method may be, for example, a method of loading the plug-in faster than the second loading method; the second loading method may be, for example, a ratio of space occupied by loading the plug-in The first loading mode is a smaller mode. The first loading mode may be, for example, a speed mode, and the second loading mode may be a quick mode.

In the embodiment of the present application, after receiving the instruction that triggers the loading of the plug-in, the configuration information of the plug-in is first obtained, and the plug-in can be loaded according to the configuration information. Since the configuration information is generated based on the loading setting of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is an interface for configuring all plug-ins of the application, the same configuration can be performed through the plug-in configuration interface Each plug-in of the application is configured separately, so that each plug-in can be loaded in different ways. This ensures that different plug-ins of the same application have multiple loading methods, and the flexibility is high. When loading different plug-ins of the same application, the same loading method is used, which leads to the problem of poor flexibility.

In an embodiment of the present invention, after receiving the instruction that triggers the loading of the plug-in in step 110, the method for loading a plug-in of an application provided by the embodiment of the present invention may further include: displaying a prompt for whether to optimize the plug-in Information; receive instructions for optimizing the plug-in. Correspondingly, obtaining the configuration information of the plug-in in step 120 includes acquiring configuration information of the plug-in when receiving an instruction for optimizing the plug-in.

The information for prompting whether to optimize the plug-in may be "whether to optimize the plug-in". The display can be in the form of a text box or a picture. The display interface may include two options, yes and no. When the user selects Yes, an instruction to optimize the plug-in can be received. When the user selects No, an instruction to not optimize the plug-in may be received. When receiving the instruction not to optimize the plug-in, it can be loaded according to the traditional loading method; when receiving the instruction to optimize the plug-in, the configuration information of the plug-in can be obtained .

In the embodiment of the present invention, by displaying information for prompting whether to optimize the plug-in, the loading method of the plug-in can be optimized according to the user's needs, so that the user's needs can be better met.

In the embodiment of the present invention, acquiring the configuration information of the plug-in in step 120 may be applicable to the case where the plug-in is started for the first time and not for the first time.

In an embodiment of the present invention, in the case where the plug-in is first started, before receiving the instruction that triggers the loading of the plug-in in step 110, the method for loading a plug-in of an application provided by an embodiment of the present invention may further include: displaying the plug-in Configuration interface; obtaining the first loading setting for the plug-in through the plug-in configuration interface; storing the first loading setting in a designated location. Correspondingly, obtaining the configuration information of the plug-in in step 110 includes: obtaining the configuration information obtained based on the first loading setting from the specified location. After acquiring the configuration information of the plug-in, the configuration information of the plug-in may also be written into an XML configuration file in the terminal.

In the embodiment of the present invention, the first startup mode of the plug-in can be set through the plug-in configuration interface, so the range of the plug-in setting is expanded, and the flexibility of the plug-in setting can be further improved to better meet user needs.

In an embodiment of the present invention, when the plug-in is not started for the first time, the XML configuration file of the terminal already contains the configuration information of the plug-in. At this time, the configuration information of the plug-in can be obtained by reading the XML configuration file. Specifically, in this case, the acquiring the configuration information of the plug-in in step 120 may include: reading the XML configuration file in the terminal when the number of times the plug-in is activated is greater than one; The configuration information of the plug-in is obtained from the XML configuration file.

The method for loading a plug-in of an application provided by an embodiment of the present invention can easily obtain the configuration information of the current plug-in by reading an XML configuration file, and then load the plug-in based on the loading mode indicated by the obtained configuration information. Later, when the loading method of the plug-in needs to be modified, the loading method of the plug-in can be modified through the plug-in configuration interface, and the configuration information of the plug-in in the XML configuration file can be further modified accordingly.

In an embodiment of the present invention, after the plug-in is loaded in step 130, in a case where the plug-in loading mode needs to be modified, the plug-in loading method may be modified through the plug-in configuration interface. Specifically, after step 130, the method for loading a plug-in of an application provided by an embodiment of the present invention may further include; displaying the plug-in configuration interface; obtaining a second loading setting for the plug-in through the plug-in configuration interface; based on The second loading setting updates configuration information of the plug-in in the XML configuration file in the terminal.

In the embodiment of the present invention, after the plug-in is loaded, the user can modify the loading method of the current plug-in through the plug-in configuration interface, and the terminal can obtain the loading setting of the plug-in through the plug-in configuration interface (second loading setting) ), and can update the configuration information of the current plug-in in the XML configuration file according to the obtained loading settings. For example, the user can load the plug-in A through the plug-in configuration interface, for example, from quick modification to acceleration, and then the terminal can modify the loading method included in the configuration information of the plug-in in the XML configuration file from quick modification to acceleration. The next time the plugin is loaded, it can be installed directly and accelerated by reading the XML configuration file.

In the embodiment of the present invention, the plug-in configuration interface can be used to flexibly configure the next loading mode of the plug-in after the plug-in is loaded, so as to better meet user needs.

2 is a flowchart of a method for loading an application plug-in provided by an embodiment of the present invention. Referring to FIG. 2, the method for loading an application plug-in provided by an embodiment of the present invention may include the following steps.

Step 210: Receive an instruction that triggers the loading of the plug-in.

In the embodiment of the present invention, when the user clicks on a certain plug-in of the application, the terminal can receive an instruction that triggers the loading of the plug-in.

Step 220, displaying information for prompting whether to optimize the plug-in, and determining whether to optimize the plug-in. If the plug-in is not optimized, step 222 is performed; if the plug-in is optimized, step 230 and subsequent steps are performed.

In the embodiment of the present invention, taking a mobile phone as an example, a monitoring subsystem may be added to the Android RunTime (ART) system of the mobile phone terminal, and the monitoring subsystem will monitor the running status in ART in real time when a certain When the application tries to start the plug-in for the first time, it will use Android's DexClassloader mechanism to load the plug-in. At this time, the monitoring subsystem will be triggered and the decision subsystem will be notified to make a decision.

After the determination subsystem receives the notification from the monitoring subsystem, it can use the public interface provided in the Activity Management Service (AMS) to obtain the name of the currently started application, and pop up a prompt to the user to let the user choose whether to be willing Optimize the plug-in that will be launched soon, so that the startup speed of the application is accelerated. Some storage space may be increased during the optimization process.

Step 222: Load the plug-in according to the original loading method.

When the user chooses not to optimize the plug-in, he can directly enter the non-optimized loading mode. The loading method of the plug-in is, for example, the quick mode by default, and the plug-in starts normally.

Step 230: Receive an instruction for optimizing the plug-in.

When the user selects that the plug-in needs to be optimized, the plug-in loading optimization process may be performed, for example, step 240 and subsequent steps are performed.

Step 240: Determine whether the plug-in is started for the first time.

Step 250: When the plug-in is started for the first time, obtain the configuration information of the plug-in from the specified location, and write the configuration information into the XML configuration file in the terminal.

The configuration information of the designated location is the configuration information stored in the designated location before step 210. Specifically, before step 210, the terminal may display the plug-in configuration interface according to user needs (for example, according to the user's trigger operation for displaying the plug-in configuration interface), and obtain the first loading of the plug-in through the plug-in configuration interface Setting, and storing the first loading setting in the designated location. Wherein, the plug-in configuration interface is an interface for configuring all plug-ins of the application.

In the embodiment of the present invention, the plug-in configuration interface may view an entry for an already started application with a plug-in function, through which the plug-in that has been loaded on the terminal (such as a mobile phone) can be viewed, and the plug-in management and configuration can be dynamically performed . At the same time, the plug-in configuration interface also allows users to re-optimize plug-ins that have not been optimized.

Step 260: When the plug-in is not started for the first time, read an XML configuration file in the terminal, and obtain configuration information of the plug-in from the XML configuration file.

Step 270: Load the plug-in according to the obtained configuration information.

The configuration information includes a first loading mode and a second loading mode. Wherein, the first loading method is a method that has a faster loading speed than the second loading method, but occupies more space than the second loading method.

Step 280: Receive a trigger operation for displaying the plug-in configuration interface, and display the plug-in configuration interface.

Among them, the plug-in configuration interface can provide a portal for viewing applications that have been started with plug-in functions. Through this portal, you can view the plug-ins that have been loaded on the terminal (mobile phone), and can dynamically manage and configure the plug-in, allowing users to Plug-ins that have not been optimized are optimized again. When the user optimizes the started plug-in, it can modify the configuration information of the plug-in in the XML configuration file (such as packages.xml) that has been stored, and can record the user's configuration of the plug-in. When the user starts the plug-in again next time, for example, when loading the DexClassloader, the plug-in can be optimized again, for example, the optimization mode is speed mode.

Step 290: Obtain the second loading setting for the plugin through the plugin configuration interface, and update the configuration information of the plugin in the XML configuration file in the terminal based on the second loading setting.

In the embodiment of the present application, after receiving the instruction that triggers the loading of the plug-in, the configuration information of the plug-in is first obtained, and the plug-in can be loaded according to the configuration information. Since the configuration information is generated based on the loading setting of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is an interface for configuring all plug-ins of the application, the same configuration can be performed through the plug-in configuration interface Each plug-in of the application is configured separately, so that each plug-in can be loaded in different ways. This ensures that different plug-ins of the same application have multiple loading methods, and the flexibility is high. When loading different plug-ins of the same application, the same loading method is used, which leads to the problem of poor flexibility.

In the embodiment of the present invention, by allowing the user to configure the optimization of the application plug-in through the plug-in configuration interface, the startup optimization of the user-focused plug-in is achieved, which can speed up the startup speed of the plug-in, and thus also can accelerate the switching of the application in the process of starting the plug-in Speed improves user experience.

FIG. 3 is a structural block diagram of an apparatus for loading an application plug-in provided by an embodiment of the present invention. Referring to FIG. 3, an apparatus 300 for loading an application plug-in provided by an embodiment of the present invention may include: a receiving module 310, an obtaining module 320, and a loading module 330. Wherein: the receiving module 310 is used to receive an instruction that triggers the loading of the plug-in; the obtaining module 320 is used to obtain the configuration information of the plug-in, the configuration information is generated based on the loading setting of the plug-in on the plug-in configuration interface, The plug-in configuration interface is an interface for configuring all plug-ins of the application; a loading module 330 is configured to load the plug-in according to the configuration information acquired by the acquiring module 320.

The device for loading a plug-in of an application provided by an embodiment of the present application will first obtain configuration information of the plug-in after receiving an instruction that triggers the loading of the plug-in, and may load the plug-in according to the configuration information. Since the configuration information is generated based on the loading setting of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is an interface for configuring all plug-ins of the application, the same configuration can be performed through the plug-in configuration interface Each plug-in of the application is configured separately, so that each plug-in can be loaded in different ways. This ensures that different plug-ins of the same application have multiple loading methods, and the flexibility is high. When loading different plug-ins of the same application, the same loading method is used, which leads to the problem of poor flexibility.

In an embodiment of the present invention, the device 300 further includes a display module for: after the receiving module receives an instruction to trigger loading of the plug-in, display information for prompting whether to optimize the plug-in; The receiving module 310 is further configured to receive an instruction for optimizing the plug-in; the acquiring module 320 is specifically configured to: when the instruction for optimizing the plug-in is received, acquire the configuration of the plug-in information.

In an embodiment of the present invention, the device 300 further includes a display module, configured to display the plug-in configuration interface before the receiving module receives an instruction that triggers the loading of the plug-in. Correspondingly, the obtaining module 320 is further configured to obtain the first loading setting of the plug-in through the plug-in configuration interface. The device 300 further includes a storage module for storing the first loading setting at a designated location. Correspondingly, in the process of obtaining the configuration information of the plug-in, the obtaining module 320 may be specifically configured to obtain the configuration information obtained based on the first loading setting from the specified location. Correspondingly, the device 300 may further include: a writing module, configured to write the configuration information of the plug-in into the XML configuration in the terminal after the acquiring module 310 obtains the configuration information of the plug-in File.

In an embodiment of the present invention, during the process of acquiring the configuration information of the plug-in, the acquiring module 320 is specifically configured to: read the XML in the terminal when the number of startups of the plug-in is greater than one Configuration file; obtaining configuration information of the plug-in from the XML configuration file.

In an embodiment of the present invention, the device 300 further includes: a display module, configured to display the plug-in configuration interface after the receiving module receives an instruction that triggers the loading of the plug-in. Correspondingly, the obtaining module 320 can also be used to obtain the second loading setting of the plugin through the plugin configuration interface. The device 300 may further include: an update module, configured to update the configuration information of the plug-in in the XML configuration file in the terminal based on the second loading setting.

In an embodiment of the present invention, the configuration information includes a first loading mode and a second loading mode. Wherein, the first loading method is a method that has a faster loading speed than the second loading method, but occupies more space than the second loading method.

An embodiment of the present application further provides a terminal, and FIG. 4 is a schematic structural diagram of the terminal provided by the embodiment of the present application. As shown in FIG. 4, the terminal may have a relatively large difference due to different configurations or performances, and may include one or more processors 401 and a memory 402, and the memory 402 may store one or more stored application programs or data. Among them, the memory 402 may be short-term storage or persistent storage. The application program stored in the memory 402 may include one or more modules (not shown), and each module may include a series of computer programs in the terminal. Furthermore, the processor 401 may be configured to communicate with the memory 402 and execute a series of computer programs in the memory 402 on the terminal. The terminal may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input/output interfaces 405, one or more keyboards 406, and so on.

In a specific embodiment, the terminal includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, the following process is implemented: receiving An instruction to trigger loading of the plug-in; obtaining configuration information of the plug-in, the configuration information is generated based on loading settings of the plug-in on the plug-in configuration interface, and the plug-in configuration interface configures all plug-ins of the application Interface; load the plug-in according to the configuration information.

After receiving the instruction that triggers the loading of the plug-in, the terminal provided in the embodiment of the present application will first obtain the configuration information of the plug-in, and may load the plug-in according to the configuration information. Since the configuration information is generated based on the loading setting of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is an interface for configuring all plug-ins of the application, the same configuration can be performed through the plug-in configuration interface Each plug-in of the application is configured separately, so that each plug-in can be loaded in different ways. This ensures that different plug-ins of the same application have multiple loading methods, and the flexibility is high. When loading different plug-ins of the same application, the same loading method is used, which leads to the problem of poor flexibility.

In an embodiment, when the computer program is executed by the processor, the computer program may further perform the following operation: after receiving the instruction that triggers loading of the plug-in, display information for prompting whether to optimize the plug-in; Receiving an instruction for optimizing the plug-in; when receiving an instruction for optimizing the plug-in, acquiring configuration information of the plug-in.

In an embodiment, when the computer program is executed by the processor, the computer program may further perform the following operations: when the plug-in is first started, displaying the plug-in configuration interface; acquiring the pair through the plug-in configuration interface The first loading setting performed by the plug-in; storing the first loading setting in a designated location; obtaining configuration information based on the first loading setting from the designated location; acquiring the configuration of the plugin After the information, the configuration information of the plug-in is written into the XML configuration file in the terminal.

In an embodiment, when the computer program is executed by the processor, it may also perform the following operations: when the number of startups of the plug-in is greater than 1, reading the XML configuration file in the terminal; The configuration information of the plug-in is obtained from the XML configuration file.

In an embodiment, when the computer program is executed by the processor, the computer program may also perform the following operations: after loading the plug-in, displaying the plug-in configuration interface; acquiring the plug-in configuration interface through the plug-in configuration interface A second loading setting performed by the plug-in; based on the second loading setting, updating configuration information of the plug-in in the XML configuration file in the terminal.

In the embodiment of the present invention, the configuration information includes a first loading mode and a second loading mode; wherein, the first loading mode is a way to load the plug-in faster than the second loading mode The second loading mode is a way that the space occupied by loading the plug-in is smaller than that of the second loading mode.

In addition, an embodiment of the present application also provides a non-transitory computer-readable storage medium, where the storage medium is used to store a computer program, and when the computer program is executed by a processor, any kind of loading provided by the embodiment of the present invention is implemented. Steps in the method of applying the plug-in. For example, when the computer program is executed by the processor, the following operations are performed: receiving an instruction that triggers the loading of the plug-in; acquiring configuration information of the plug-in, which is generated based on the loading setting of the plug-in on the plug-in configuration interface The plug-in configuration interface is an interface for configuring all plug-ins of the application; according to the configuration information, the plug-in is loaded.

The computer readable storage medium provided by the embodiment of the present application will first obtain the configuration information of the plug-in after receiving the instruction that triggers the loading of the plug-in, and may load the plug-in according to the configuration information. Since the configuration information is generated based on the loading setting of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is an interface for configuring all plug-ins of the application, the same configuration can be performed through the plug-in configuration interface Each plug-in of the application is configured separately, so that each plug-in can be loaded in different ways. This ensures that different plug-ins of the same application have multiple loading methods, and the flexibility is high. When loading different plug-ins of the same application, the same loading method is used, which leads to the problem of poor flexibility.

The computer-readable storage medium includes read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk, or optical disk.

In addition, an embodiment of the present invention also provides a computer program product. The computer program product includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are When executed by a computer, the computer is caused to execute the method in any of the above method embodiments.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

The present invention is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and/or block in the flowchart and/or block diagram and a combination of the flow and/or block in the flowchart and/or block diagram may be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processing machine, or other programmable data processing device to produce a machine that enables the generation of instructions executed by the processor of the computer or other programmable data processing device A device for realizing the functions specified in one block or multiple blocks of one flow or multiple flows of a flowchart and/or one block or multiple blocks of a block diagram.

These computer program instructions may also be stored in a computer readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, the instructions The device implements the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are performed on the computer or other programmable device to produce computer-implemented processing, which is executed on the computer or other programmable device The instructions provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.

In a typical configuration, the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include non-permanent memory, random access memory (RAM) and/or non-volatile memory in a computer-readable medium, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including permanent and non-permanent, removable and non-removable media, can store information by any method or technology. The information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. As defined in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device that includes a series of elements not only includes those elements, but also includes Other elements not explicitly listed, or include elements inherent to such processes, methods, goods, or equipment. Without more restrictions, the element defined by the sentence "include one..." does not exclude that there are other identical elements in the process, method, commodity or equipment that includes the element.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

The embodiments in this specification are described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method embodiment.

The above is only an embodiment of the present application, and is not intended to limit the present application. For those skilled in the art, this application may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the scope of the claims of this application.

Claims (13)

1. A method for loading an application plug-in is applied to a terminal, wherein the method includes:

   Receive instructions that trigger plugin loading;

   Acquiring configuration information of the plug-in, the configuration information is generated based on loading settings of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is an interface for configuring all plug-ins of the application;

   According to the configuration information, load the plug-in.
2. The method according to claim 1, wherein after the instruction that triggers the loading of the plug-in is received, the method further comprises:

   Displaying information for prompting whether to optimize the plug-in;

   Receiving instructions for optimizing the plug-in;

   The acquiring configuration information of the plug-in includes: acquiring configuration information of the plug-in when receiving an instruction for optimizing the plug-in.
3. The method according to claim 1, wherein before the receiving the instruction that triggers the loading of the plug-in, the method further comprises:

   When the plug-in is started for the first time, perform the following operations:

   Display the plug-in configuration interface;

   Obtaining the first loading setting for the plug-in through the plug-in configuration interface;

   Storing the first loading setting in a designated location;

   The acquiring configuration information of the plug-in includes: acquiring the configuration information obtained based on the first loading setting from the specified location;

   After acquiring the configuration information of the plug-in, the method further includes: writing the configuration information of the plug-in into an extensible markup language XML configuration file in the terminal.
4. The method according to claim 1, wherein the acquiring configuration information of the plug-in includes:

   When the number of startups of the plug-in is greater than 1, read the XML configuration file in the terminal;

   Obtain the configuration information of the plug-in from the XML configuration file.
5. The method according to claim 1, wherein after the loading the plug-in, the method further comprises;

   Display the plug-in configuration interface;

   Obtaining the second loading setting for the plug-in through the plug-in configuration interface;

   Based on the second loading setting, the configuration information of the plug-in in the XML configuration file in the terminal is updated.
6. The method according to claim 1, wherein the configuration information includes a first loading mode and a second loading mode;

   Wherein, the first loading mode is a way to load the plug-in faster than the second loading mode;

   The second loading mode is a way that the space occupied by loading the plug-in is smaller than that of the first loading mode.
7. A device for loading an application plug-in, including:

   The receiving module is used to receive the instruction that triggers the loading of the plug-in;

   An acquiring module, configured to acquire configuration information of the plug-in, the configuration information is generated based on loading settings of the plug-in on the plug-in configuration interface, and the plug-in configuration interface is configured for all plug-ins of the application interface;

   The loading module is configured to load the plug-in according to the configuration information obtained by the obtaining module.
8. The apparatus according to claim 7, wherein the apparatus further comprises a display module for: after the receiving module receives an instruction to trigger loading of the plug-in, displaying information for prompting whether to optimize the plug-in;

   The receiving module is also used to receive instructions for optimizing the plug-in;

   The acquiring module is configured to acquire configuration information of the plug-in when receiving an instruction for optimizing the plug-in.
9. The device according to claim 7, wherein the device further comprises a display module for displaying the plug-in configuration interface before the receiving module receives an instruction that triggers the loading of the plug-in;

   The obtaining module is further configured to obtain the first loading setting for the plug-in through the plug-in configuration interface;

   The device further includes a storage module for storing the first loading setting at a designated location;

   In the process of acquiring the configuration information of the plug-in, the acquiring module is configured to acquire the configuration information obtained based on the first loading setting from the specified location;

   The device further includes a writing module for writing the configuration information of the plug-in into the XML configuration file of the extensible markup language in the terminal after the acquisition module obtains the configuration information of the plug-in .
10. The apparatus according to claim 7, wherein in the process of acquiring the configuration information of the plug-in, the acquiring module is configured to:

    In the case that the number of startups of the plug-in is greater than 1, reading the XML configuration file in the terminal;

    Obtain the configuration information of the plug-in from the XML configuration file.
11. The device according to claim 7, wherein the device further comprises:

    A display module, configured to display the plug-in configuration interface after the receiving module receives an instruction that triggers the loading of the plug-in;

    The acquiring module is further configured to: acquire a second loading setting for the plug-in through the plug-in configuration interface;

    The device further includes an update module for updating the configuration information of the plug-in in the XML configuration file in the terminal based on the second loading setting.
12. A terminal, including a memory and a processor, a computer program is stored on the memory, and when the computer program is executed, the steps in the method according to any one of claims 1 to 6 are implemented.
13. A non-transitory computer-readable storage medium, wherein a computer program is stored on the storage medium, and when the computer program is executed, the steps in the method according to any one of claims 1 to 6 are implemented.

Images