Plug-in management method and device, electronic equipment and storage medium

Abstract

The invention provides a plug-in management method and device, electronic equipment and a storage medium, and relates to the technical field of software development. The method comprises the steps that in response to starting operation of a target application program, a main interface corresponding to the target application program is displayed, a plug-in management interface corresponding to a target management plug-in is displayed on the main interface corresponding to the target application program, and the plug-in management interface comprises a plug-in management list and a plug-in management module; the plug-in management list displays a plug-in tag of at least one other plug-in accessed to the target application program; and in response to a trigger operation on a first target plug-in label in the plug-in management list, starting the first target plug-in to call the function logic corresponding to the first target plug-in, so that the function logic corresponding to the first target plug-in is called under the condition that a plurality of other plug-ins are installed in the target application program. The plug-in labels corresponding to the multiple other plug-ins can be displayed in a centralized mode through the plug-in management list, rapid searching can be achieved through the plug-in management list, and the plug-in calling efficiency and the plug-in management efficiency are improved.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a plug-in management method, device, electronic device and storage medium. Background Art

[0002] A plug-in is a software component designed to extend or modify the functionality of an existing application. By installing a plug-in, users can add new features to an application or improve its performance without making large-scale changes to the main program.

[0003] In the prior art, when multiple plug-ins are installed in an application, if a specific plug-in needs to be used, it is often necessary to search to find the specific plug-in.

[0004] It can be seen that the existing plug-in management method has the problems of low calling efficiency and low management efficiency. Summary of the invention

[0005] The purpose of the present application is to provide a plug-in management method, device, electronic device and storage medium to improve the efficiency of plug-in calling and plug-in management in view of the deficiencies in the above-mentioned prior art.

[0006] To achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0007] In a first aspect, the present invention provides a plug-in management method, the method comprising:

[0008] In response to a start-up operation of a target application, a main interface corresponding to the target application is displayed, and a plug-in management interface corresponding to a target management plug-in is displayed on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, wherein the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application;

[0009] In response to a triggering operation on a first target plug-in tag in the plug-in management list, the first target plug-in is started to call a functional logic corresponding to the first target plug-in.

[0010] In a second aspect, the present invention provides a plug-in management device, comprising:

[0011] A display module is used to display a main interface corresponding to the target application in response to a start operation of the target application, and to display a plug-in management interface corresponding to the target management plug-in on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, wherein the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application;

[0012] The startup module is used to start the first target plug-in in response to the trigger operation of the first target plug-in tag in the plug-in management list to call the functional logic corresponding to the first target plug-in.

[0013] In a third aspect, the present invention provides an electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the plug-in management method as described in any of the aforementioned implementations.

[0014] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the plug-in management method as described in any of the aforementioned implementations are executed.

[0015] The beneficial effects of this application are:

[0016] In the plug-in management method, device, electronic device and storage medium provided by the embodiments of the present application, in response to the start-up operation of the target application, the main interface corresponding to the target application is displayed, and the plug-in management interface corresponding to the target management plug-in is displayed on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, the plug-in management list displays the plug-in tag of at least one other plug-in connected to the target application; in response to the triggering operation of the first target plug-in tag in the plug-in management list, the first target plug-in is started to call the functional logic corresponding to the first target plug-in, so that when the target application has multiple other plug-ins installed, the plug-in tags corresponding to the multiple other plug-ins can be centrally displayed through the plug-in management list, and then the user can quickly find the first plug-in tag corresponding to the first target plug-in that he expects to call through the plug-in management list, which can improve the plug-in calling efficiency and plug-in management efficiency compared with the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 A flowchart of a plug-in management method provided in an embodiment of the present application;

[0019] Figure 2A flowchart of another plug-in management method provided in an embodiment of the present application;

[0020] Figure 3 A flowchart of another plug-in management method provided in an embodiment of the present application;

[0021] Figure 4 A schematic diagram of a plug-in management interface provided in an embodiment of the present application;

[0022] Figure 5 A flowchart of another plug-in management method provided in an embodiment of the present application;

[0023] Figure 6 A flowchart of another plug-in management method provided in an embodiment of the present application;

[0024] Figure 7 A flowchart of another plug-in management method provided in an embodiment of the present application;

[0025] Figure 8 A schematic diagram of functional modules of a plug-in management device provided in an embodiment of the present application;

[0026] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0028] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0029] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0030] In the prior art, when multiple plug-ins are installed in an application, if a specific plug-in needs to be used, it is often necessary to search to find the specific plug-in. Therefore, the existing plug-in management method has the problems of low calling efficiency and low management efficiency.

[0031] In view of this, an embodiment of the present application provides a plug-in management method, which can be applied to implement quick calling of a target plug-in among multiple plug-ins, thereby improving plug-in calling efficiency and plug-in management efficiency.

[0032] Figure 1 The flowchart of a plug-in management method provided in the embodiment of the present application is shown in FIG. The execution subject of the method can be a computer, a server, a processor, or other electronic device that can install an application program, and is not limited here. Figure 1 As shown, the method includes:

[0033] Step 101: In response to a start-up operation of a target application, a main interface corresponding to the target application is displayed, and a plug-in management interface corresponding to a target management plug-in is displayed on the main interface corresponding to the target application.

[0034] The plug-in management interface includes: a plug-in management list, and the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application.

[0035] In some embodiments, the target application may be graphics software, communication software, office software, security software, engineering software, etc., which are not limited here. In order to better understand the present application, the following embodiments are described by taking the target application as graphics software, such as Blender software, as an example. Of course, the type of the target application is not limited thereto.

[0036] It should be noted that the target application may be installed with a target management plug-in and at least one other plug-in. The target management plug-in can be used to manage the plug-ins in the target application, and it can provide an entry for modular plug-ins to access the target application software. Optionally, the target management plug-in can be a framework plug-in, and other plug-ins can be connected to the target management plug-in in a modular manner to achieve modular development. It is understandable that if the target application is Blender software, then the other plug-ins are Blender plug-ins.

[0037] Optionally, the startup operation may be a trigger operation acting on a shortcut icon corresponding to the target application, such as a long press operation, a single click operation, a double click operation, etc., which are not limited here. In response to the startup operation, the target application may be started and the main interface corresponding to the target application may be displayed. While the main interface corresponding to the target application is displayed, the plug-in management interface corresponding to the target management plug-in may be displayed in the main interface.

[0038] The plug-in management interface corresponding to the target management plug-in may provide a plug-in management list, which may be used to display the plug-in label of at least one other plug-in installed by the target application. In some embodiments, the plug-in label may include a plug-in name, a plug-in icon, etc., which are not limited here. Optionally, different plug-ins may correspond to different plug-in icons to facilitate quick identification by the user.

[0039] In some embodiments, the method of managing at least one other plug-in through the plug-in management list may include but is not limited to: managing the display position, display order, display style, display quantity, etc. of each plug-in tag in the plug-in management list, which is not limited here and can be flexibly set according to the actual application scenario.

[0040] Optionally, the plug-in management interface corresponding to the target management plug-in can be displayed in a preset area of ​​the main interface, for example, it can be displayed in the left area, right area, upper area, lower area, etc. of the main interface, without limitation here; the plug-in management list can be displayed in the center area, left area, right area, upper area, lower area, etc. of the plug-in management interface, without limitation here, and can be flexibly set according to the actual application scenario and user habits.

[0041] Step 102: In response to a trigger operation on a first target plug-in tag in the plug-in management list, start the first target plug-in to call a functional logic corresponding to the first target plug-in.

[0042] The first target plug-in tag may be a plug-in tag of the first target plug-in that the user expects to call in the plug-in management list, which is not limited here; the first target plug-in is the plug-in indicated by the first target plug-in tag.

[0043] It can be understood that, since the plug-in tags of each plug-in can be directly displayed in the plug-in management list, the user can quickly find the first plug-in tag corresponding to the first target plug-in that he expects to call through the plug-in management list during use; optionally, at this time, the first target plug-in tag can be acted on by single-clicking, double-clicking, long pressing, etc. to generate a trigger operation for the first target plug-in tag, and the first target plug-in can be started in response to the trigger operation.

[0044] Optionally, by starting the first target plug-in, the logic function corresponding to the first target plug-in can be called. It can be understood that different first target plug-ins can correspond to different logic functions, which is not limited here. Of course, in some scenarios, if the first target plug-in includes multiple logic functions, the main interface corresponding to the first target plug-in can also be displayed first, and further selection can be made through the main interface corresponding to the first target plug-in, which is not limited here.

[0045] In summary, an embodiment of the present application provides a plug-in management method, the method comprising: in response to a start-up operation of a target application, displaying a main interface corresponding to the target application, and displaying a plug-in management interface corresponding to the target management plug-in on the main interface corresponding to the target application, wherein the plug-in management interface comprises: a plug-in management list, the plug-in management list displays a plug-in tag of at least one other plug-in connected to the target application; in response to a trigger operation on a first target plug-in tag in the plug-in management list, starting the first target plug-in to call the functional logic corresponding to the first target plug-in, thereby achieving that when the target application has multiple other plug-ins installed, the plug-in tags corresponding to the multiple other plug-ins can be centrally displayed through the plug-in management list, and then the user can quickly find the first plug-in tag corresponding to the first target plug-in that he expects to call through the plug-in management list, which can improve the plug-in calling efficiency and plug-in management efficiency compared to the prior art.

[0046] Figure 2 A flowchart of another plug-in management method provided in an embodiment of the present application. In an optional implementation, as Figure 2 As shown, the plug-in management interface corresponding to the target management plug-in is displayed on the main interface corresponding to the target application, including:

[0047] Step 201: Scan the plug-in folder under the preset target path.

[0048] The preset target path may be a specified path, which is the storage path of the plug-in folder corresponding to each other plug-in. Optionally, one other plug-in may correspond to a plug-in folder, which may be used to store scripts related to other plug-ins.

[0049] In some embodiments, the preset target path may be the path indicated by the subfile of the target file corresponding to the target management plug-in, so that after finding the target file corresponding to the target management plug-in, the plug-in folder can be quickly scanned under the target file to improve scanning efficiency. In addition, setting the preset target path to the path indicated by the subfile of the target file corresponding to the target management plug-in also facilitates the administrator to quickly locate the plug-in folder corresponding to other plug-ins and manage the related scripts under the plug-in folder.

[0050] It should be noted that the target file corresponding to the target management plug-in may store the initialization script, startup script, function logic script, interface script, etc. corresponding to the target management plug-in, which is not limited here.

[0051] Step 202: If the name of the plug-in folder meets the preset requirements, determine the plug-in tag according to the name of the plug-in folder.

[0052] Step 203: Display the plug-in management interface corresponding to the target management plug-in on the main interface corresponding to the target application program according to the plug-in tag.

[0053] The preset requirement is that the name of the plug-in folder should carry the plug-in label and include preset characters, such as bp_tool_. Of course, the setting of the preset requirement is not limited to this.

[0054] Optionally, during the scanning process, the name of each plug-in folder can be obtained to determine whether the name of each plug-in folder meets the preset requirements. If yes, the name of the plug-in folder can be parsed to extract the plug-in tags of other plug-ins corresponding to the plug-in folder.

[0055] After obtaining the plug-in tags of each other plug-in, the plug-in management interface corresponding to the target management plug-in can be displayed on the main interface corresponding to the target application. It can be understood that the plug-in management list in the plug-in management interface will display the plug-in tags corresponding to the other plug-ins.

[0056] For example, the preset requirements are: the plug-in folder is named in the bp_tool_A format, where A represents the plug-in label corresponding to the plug-in folder; for example, a plug-in folder is named bp_tool_a. By comparison, it can be seen that the naming of the plug-in folder meets the preset requirements, and the plug-in label corresponding to the plug-in folder is a. At this time, the plug-in label a can be displayed in the plug-in management list in the plug-in management interface.

[0057] It can be understood that by applying this method, the plug-in tags of other plug-ins installed in the target application software can be quickly determined and displayed, thereby improving the efficiency of plug-in management. In particular, when the target application software has many other plug-ins installed, the applicability of the method of this application can be improved.

[0058] In an optional implementation, the plug-in folder includes the following scripts: a plug-in initialization script, a plug-in startup script, a plug-in function logic script, and a plug-in interface script.

[0059] Optionally, the folder structure between the plug-in folders corresponding to each other plug-in and the target folder corresponding to the target management plug-in is as follows:

[0060]

[0061] Among them, the initialization script corresponding to the target management plug-in and the plug-in folder corresponding to other plug-ins are the same-level directories, and both are subdirectories of the target folder corresponding to the target management plug-in. Optionally, the __init__.py script can contain code to register its display interface with the target application, such as bpy.utils.register_class(), and code to unregister the display interface in the target application, such as bpy.utils.unregister_class(), but is not limited to this.

[0062] Optionally, the __init__.py script can be used to create the main interface corresponding to the target management plug-in, providing an entry for the modular plug-in to access the target application, that is, the plug-in label carried in the plug-in folder bp_tool_a in its directory is used as the name of this plug-in, and then the code in the plug-in folder bp_tool_a is imported as a module into the main program of the target management plug-in through the import_module function in the Python standard library importlib, that is, all plug-in folders placed in the Toolkit directory are called as a module by the main program of the (target management plug-in) framework and displayed in the target application, so that each plug-in is quickly deployed to the framework as a separate module. Among them, the import_module function is used to dynamically import a module.

[0063] In addition, when the main program of the framework writes the registration and deregistration information of the Blender plug-in, the imported plug-in codes, that is, the historical import records, can be obtained through the dictionary sys.modules in the Python standard library. Among them, sys.modules is a dictionary in the Python standard library, which stores all the modules that have been imported currently. Its main function is to cache the imported modules to avoid repeated imports.

[0064] Based on the above content, the relationship between the scripts is: the plug-in initialization script can call the plug-in interface script, and the plug-in startup script can call the plug-in function logic script.

[0065] Figure 3 A flowchart of another plug-in management method provided in an embodiment of the present application. In an optional implementation, as Figure 3 As shown, in response to the triggering operation on the first target plug-in tag in the plug-in management list, starting the first target plug-in corresponding to the first target plug-in tag to call the functional logic corresponding to the first target plug-in includes:

[0066] Step 301: In response to a trigger operation on a first target plug-in tag in a plug-in management list, a plug-in initialization script is run.

[0067] Optionally, the first target plug-in tag can be acted on by single-clicking, double-clicking, long pressing, etc. to generate a trigger operation for the first target plug-in tag. In response to the trigger operation, a plug-in initialization script can be run, and the basic configuration of the plug-in can be set through the plug-in initialization script, such as registering the plug-in to the target application software, so that the target application software can recognize and load the plug-in, load necessary resources, and initialize global variables.

[0068] Step 302: Call the plug-in interface script through the plug-in initialization script, and display the main interface corresponding to the first target plug-in according to the plug-in interface script.

[0069] In addition, during the running of the plug-in initialization script, the plug-in interface script can also be called, and the plug-in interface script can be used to create and manage the user interface of the plug-in, such as dialog boxes, menu items, etc. It can be understood that by running the plug-in interface script, the main interface corresponding to the first target plug-in can be displayed, and the main interface corresponding to the first target plug-in can include one or more function controls corresponding to the first target plug-in, and each function control can realize different functions when triggered.

[0070] Step 303: In response to a triggering operation on a target function control in a main interface corresponding to the first target plug-in, a plug-in startup script is executed.

[0071] Among them, according to the actual application scenario, any function control can be selected as the target function control in the main interface corresponding to the first target plug-in, and the target function control can be acted on through touch methods such as single-click, double-click, and long press to generate a corresponding trigger operation; in response to the trigger operation of the target function control, the plug-in startup script can be called to execute the preprocessing operation corresponding to the target function control, such as loading the setting parameters corresponding to the target function control, but not limited to this.

[0072] Step 304: Call the plug-in function logic script through the plug-in startup script, and run the target function logic script corresponding to the target function control according to the plug-in function logic script.

[0073] In addition, the plug-in function logic script can also be called during the running of the plug-in startup script. The plug-in function logic script can include the target function logic script corresponding to the target function control. The target function logic script corresponding to the target function control can be run through the plug-in function logic script to realize the call of the target function corresponding to the target function control.

[0074] It should be noted that the present application does not limit the specific logic script in the plug-in function logic script, and it can be flexibly set according to the actual application scenario.

[0075] In summary, by applying the embodiments of the present application, other plug-ins can be connected to the target management plug-in in a modular manner, thereby realizing modular development and flexible development.

[0076] Figure 4 A schematic diagram of a plug-in management interface provided in an embodiment of the present application. In an optional implementation, such as Figure 4 As shown, the plug-in management interface 120 may include: a plug-in management list 121 and a setting control 122. The plug-in management list 121 displays the plug-in label of at least one other plug-in connected to the target application, for example, the plug-in labels of plug-ins a, b, c, and d may be displayed. Optionally, according to the actual application scenario, the plug-in management list 121 may also include a scroll control 128, wherein the scroll control 128 may adjust the content of the plug-in label displayed in the plug-in management list 121 in response to a trigger operation.

[0077] Optionally, based on Figure 4 The interface shown in the figure, the method further includes:

[0078] In response to the triggering operation on the setting control, the plug-in management list and / or the display style of each plug-in label in the plug-in management list are adjusted, and the display style includes a display font and / or a display color.

[0079] Optionally, the setting control can be acted on by touch methods such as single-clicking, double-clicking, long pressing, dragging, etc. to generate a corresponding trigger operation. In response to the trigger operation, the display style of the plug-in management list and / or the display style of each plug-in label in the plug-in management list can be adjusted.

[0080] For example, in some scenarios, the setting control can be used to adjust the display color of each plug-in label in the plug-in management list. Optionally, the setting can be for all plug-in labels, or for some plug-in labels. For example, different display colors can be set for each plug-in label. Of course, the specific setting method is not limited to this. In some scenarios, the setting control can also be used to adjust the display position, display size, etc. of the plug-in management list in the plug-in management interface. For example, the plug-in management list located on the left side of the plug-in management interface can be dragged to the right side of the plug-in management interface. Of course, the specific setting method is not limited to this.

[0081] Figure 5 A flowchart of another plug-in management method provided in an embodiment of the present application. Figure 4 As shown, the plug-in management interface 120 also includes: a hidden display control 123. Figure 5 As shown, the above method also includes:

[0082] Step 401: In response to a selection operation on at least some plug-in tags in a plug-in management list, a plug-in tag to be hidden is determined.

[0083] Optionally, the plug-in tags to be hidden may be some plug-in tags in the plug-in management list, for example, plug-in tags that have not been called or have been called less frequently within a preset time period (for example, a week, a month, etc.), or may be any plug-in tags specified by the user, which is not limited here.

[0084] In some embodiments, a touch method such as clicking, long pressing, sliding, etc. may be used to act on the plug-in label to be hidden to generate a corresponding selection operation.

[0085] Step 402: In response to the triggering operation of hiding the display control, the plug-in label to be hidden is cancelled in the plug-in management list.

[0086] After determining the plug-in tag to be hidden, optionally, a touch method such as single click, double click, long press, etc. can be used to act on the hide display control in the plug-in management interface to generate a corresponding trigger operation. In response to the trigger operation, the plug-in tag to be hidden can be undisplayed in the plug-in management list. It can be understood that through the hiding operation, the number of plug-in tags displayed in the plug-in management list can be reduced, so that when selecting the first target plug-in tag, the selection time can be reduced and the selection efficiency can be improved.

[0087] Optionally, continue to refer to the above Figure 4 As shown, the plug-in management interface 120 also includes: an adjustment control 124 .

[0088] Correspondingly, the above method further includes: in response to a triggering operation on the adjustment control, adjusting the display order of each plug-in label in the plug-in management list.

[0089] Optionally, the adjustment control may be acted on by a touch mode such as single-click, double-click, long-press, etc. to generate a corresponding trigger operation, and in response to the trigger operation, the display order of each plug-in label in the plug-in management list may be adjusted.

[0090] In some embodiments, when making specific adjustments, you can set the usage frequency of each other plug-in within a preset time period to count, and adjust the display order of each plug-in label in the plug-in management list according to the usage frequency of each other plug-in. Optionally, you can set the higher the usage frequency, the higher the corresponding display order.

[0091] Of course, it should be noted that, in some embodiments, in response to a trigger operation on an adjustment control, an editing mode for entering the display order can also be set. Optionally, in this editing mode, the user can flexibly adjust the display order of each plug-in label. For example, a plug-in label can be adjusted to a suitable display order according to the user's usage habits. This is not limited here and can be flexibly set according to the actual application scenario.

[0092] By applying the embodiments of the present application, it is possible to flexibly adjust the display order of each plug-in label in the plug-in management list according to the actual application scenario, thereby improving the flexibility of the method of the present application.

[0093] Figure 6 A flowchart of another plug-in management method provided in an embodiment of the present application. Figure 4 As shown, the plug-in management interface 120 also includes: a first update control 125. Figure 6 As shown, the above method also includes:

[0094] Step 501: In response to a trigger operation on a first update control, a plug-in folder under a preset target path is scanned to obtain a scan result.

[0095] Step 502: Determine the plug-in tag to be imported according to the scanning result and the historical import record, where the historical import record includes the plug-in tag currently displayed in the plug-in management list.

[0096] Step 503: Update the plug-in management list according to the plug-in tag to be imported.

[0097] Optionally, the first update control can be acted on by a touch method such as single-clicking, double-clicking, and long pressing to generate a corresponding trigger operation. In response to the trigger operation, the plug-in folder under the preset target path can be rescanned to obtain the scan results; the plug-in tags that are not recorded in the historical import records are screened and determined in the scan results as the plug-in tags to be imported; according to the plug-in tags to be imported, the plug-in management list is updated so that the updated plug-in management list includes the plug-in tag to be imported.

[0098] By applying the embodiments of the present application, when the plug-in folder under the preset target path is updated, the plug-in label displayed in the plug-in management list can be updated in time without the user restarting the target application, which can improve the flexibility and applicability of the method of the present application.

[0099] Figure 7 A flowchart of another plug-in management method provided in an embodiment of the present application. Figure 4 As shown, the plug-in management interface 120 also includes: a second update control 126. Figure 7 As shown, the above method also includes:

[0100] Step 601: In response to a selection operation on at least some plug-in tags in a plug-in management list, a plug-in tag to be updated is determined.

[0101] Step 602: In response to the triggering operation on the second update control, the plug-in folders corresponding to the plug-in tags to be updated are updated according to a preset update path.

[0102] The difference from the first update control is that the second update control is used to update the plug-in folders of other plug-ins, that is, to update the versions of each plug-in folder.

[0103] Optionally, in response to the triggering operation of the second update control, the plug-in folders corresponding to each other plug-in can be updated according to the update path corresponding to each other plug-in. The file content in each plug-in folder can be updated to the latest version through the update, which can improve the applicability of the method of the present application.

[0104] In some embodiments, when updating, the latest version of the plug-in file corresponding to each other plug-in can be downloaded through the plug-in server corresponding to each other plug-in. Of course, the specific updating method is not limited to this.

[0105] Figure 8 This is a functional module diagram of a plug-in management device provided in an embodiment of the present application. The basic principle and technical effects of the device are the same as those of the corresponding method embodiment described above. For the sake of brief description, the parts not mentioned in this embodiment can be referred to the corresponding contents in the method embodiment. Figure 8 As shown, the plug-in management device 200 includes:

[0106] The display module 210 is used to display the main interface corresponding to the target application in response to the start operation of the target application, and display the plug-in management interface corresponding to the target management plug-in on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, and the plug-in management list displays the plug-in label of at least one other plug-in connected to the target application;

[0107] The starting module 220 is used to start the first target plug-in in response to the triggering operation on the first target plug-in tag in the plug-in management list to call the functional logic corresponding to the first target plug-in.

[0108] In an optional implementation, the display module 210 is specifically used to scan the plug-in folder under the preset target path;

[0109] If the naming of the plug-in folder meets the preset requirements, determining the plug-in tag according to the naming of the plug-in folder;

[0110] According to the plug-in tag, a plug-in management interface corresponding to the target management plug-in is displayed on the main interface corresponding to the target application.

[0111] In an optional implementation, the plug-in folder includes the following scripts: a plug-in initialization script, a plug-in startup script, a plug-in function logic script, and a plug-in interface script; the startup module 220 is specifically configured to run the plug-in initialization script in response to a trigger operation on the first target plug-in tag in the plug-in management list;

[0112] Calling the plug-in interface script through the plug-in initialization script, and displaying the main interface corresponding to the first target plug-in according to the plug-in interface script;

[0113] In response to a triggering operation on a target function control in a main interface corresponding to the first target plug-in, running the plug-in startup script;

[0114] The plug-in function logic script is called through the plug-in startup script, and the target function logic script corresponding to the target function control is run according to the plug-in function logic script.

[0115] In an optional embodiment, the plug-in management interface also includes: a setting control, and the plug-in management device also includes: a response module, which is used to adjust the plug-in management list and / or the display style of each plug-in label in the plug-in management list in response to a triggering operation on the setting control, and the display style includes a display font and / or a display color.

[0116] In an optional implementation, the plug-in management interface further includes: a hidden display control, and the plug-in management device further includes: a response module, configured to determine a plug-in tag to be hidden in response to a selection operation on at least part of the plug-in tags in the plug-in management list;

[0117] In response to the triggering operation of the hide display control, the plug-in label to be hidden is undisplayed in the plug-in management list.

[0118] In an optional implementation, the plug-in management interface further includes: an adjustment control, and the plug-in management device further includes: a response module for adjusting the display order of each plug-in label in the plug-in management list in response to a triggering operation on the adjustment control.

[0119] In an optional implementation, the plug-in management interface further includes: a first update control, and the plug-in management device further includes: a response module, configured to scan the plug-in folder under the preset target path in response to a trigger operation on the first update control, and obtain a scan result;

[0120] Determining the plug-in tag to be imported according to the scanning result and the historical import record, wherein the historical import record includes the plug-in tag currently displayed in the plug-in management list;

[0121] The plug-in management list is updated according to the plug-in tag to be imported.

[0122] In an optional implementation, the plug-in management interface further includes: a second update control, and the plug-in management device further includes: a response module, configured to determine the plug-in tags to be updated in response to a selection operation on at least part of the plug-in tags in the plug-in management list;

[0123] In response to the triggering operation on the second update control, the plug-in folders corresponding to the plug-in tags to be updated are updated according to a preset update path.

[0124] The above-mentioned device is used to execute the method provided by the aforementioned embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0125] The above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), or one or more microprocessors, or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0126] Fig. 9 The following is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device can be integrated into the above-mentioned plug-in management device. Fig. 9As shown, the electronic device may include: a processor 310, a storage medium 320 and a bus 330, the storage medium 320 stores machine-readable instructions executable by the processor 310, when the electronic device is running, the processor 310 and the storage medium 320 communicate through the bus 330, the processor 310 executes the machine-readable instructions to perform the steps of the following method embodiment:

[0127] In response to a start-up operation of a target application, a main interface corresponding to the target application is displayed, and a plug-in management interface corresponding to a target management plug-in is displayed on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, wherein the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application;

[0128] In response to a triggering operation on a first target plug-in tag in the plug-in management list, the first target plug-in is started to call a functional logic corresponding to the first target plug-in.

[0129] In an optional implementation, displaying a plug-in management interface corresponding to the target management plug-in on a main interface corresponding to the target application includes:

[0130] Scan the plugin folder under the preset target path;

[0131] If the naming of the plug-in folder meets the preset requirements, determining the plug-in tag according to the naming of the plug-in folder;

[0132] According to the plug-in tag, a plug-in management interface corresponding to the target management plug-in is displayed on the main interface corresponding to the target application.

[0133] In an optional implementation, the plug-in folder includes the following scripts: a plug-in initialization script, a plug-in startup script, a plug-in function logic script, and a plug-in interface script; in response to a trigger operation on a first target plug-in tag in the plug-in management list, starting the first target plug-in to call the function logic corresponding to the first target plug-in includes:

[0134] In response to a trigger operation on a first target plug-in tag in the plug-in management list, running the plug-in initialization script;

[0135] Calling the plug-in interface script through the plug-in initialization script, and displaying the main interface corresponding to the first target plug-in according to the plug-in interface script;

[0136] In response to a triggering operation on a target function control in a main interface corresponding to the first target plug-in, running the plug-in startup script;

[0137] The plug-in function logic script is called through the plug-in startup script, and the target function logic script corresponding to the target function control is run according to the plug-in function logic script.

[0138] In an optional implementation, the plug-in management interface further includes: setting controls, and the method further includes:

[0139] In response to a triggering operation on the setting control, the plug-in management list and / or the display style of each plug-in label in the plug-in management list are adjusted, wherein the display style includes a display font and / or a display color.

[0140] In an optional implementation manner, the plug-in management interface further includes: hiding the display control, and the method further includes:

[0141] In response to a selection operation on at least some plug-in tags in the plug-in management list, determining plug-in tags to be hidden;

[0142] In response to the triggering operation of the hide display control, the plug-in label to be hidden is undisplayed in the plug-in management list.

[0143] In an optional implementation, the plug-in management interface further includes: adjusting controls, and the method further includes:

[0144] In response to the triggering operation on the adjustment control, the display order of each plug-in label in the plug-in management list is adjusted.

[0145] In an optional implementation, the plug-in management interface further includes: a first update control, and the method further includes:

[0146] In response to the triggering operation on the first update control, scanning the plug-in folder under the preset target path to obtain a scanning result;

[0147] Determining the plug-in tag to be imported according to the scanning result and the historical import record, wherein the historical import record includes the plug-in tag currently displayed in the plug-in management list;

[0148] The plug-in management list is updated according to the plug-in tag to be imported.

[0149] In an optional implementation, the plug-in management interface further includes: a second update control, and the method further includes:

[0150] In response to a selection operation on at least some of the plug-in tags in the plug-in management list, determining plug-in tags to be updated;

[0151] In response to the triggering operation on the second update control, the plug-in folders corresponding to the plug-in tags to be updated are updated according to a preset update path.

[0152] The specific implementation method and technical effects of the above method embodiment are similar to those mentioned above and will not be repeated here.

[0153] Optionally, the present application further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the following method embodiment are executed:

[0154] In response to a start-up operation of a target application, a main interface corresponding to the target application is displayed, and a plug-in management interface corresponding to a target management plug-in is displayed on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, wherein the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application;

[0155] In response to a triggering operation on a first target plug-in tag in the plug-in management list, the first target plug-in is started to call a functional logic corresponding to the first target plug-in.

[0156] In an optional implementation, displaying a plug-in management interface corresponding to the target management plug-in on a main interface corresponding to the target application includes:

[0157] Scan the plugin folder under the preset target path;

[0158] If the naming of the plug-in folder meets the preset requirements, determining the plug-in tag according to the naming of the plug-in folder;

[0159] According to the plug-in tag, a plug-in management interface corresponding to the target management plug-in is displayed on the main interface corresponding to the target application.

[0160] In an optional implementation, the plug-in folder includes the following scripts: a plug-in initialization script, a plug-in startup script, a plug-in function logic script, and a plug-in interface script; in response to a trigger operation on a first target plug-in tag in the plug-in management list, starting the first target plug-in to call the function logic corresponding to the first target plug-in includes:

[0161] In response to a trigger operation on a first target plug-in tag in the plug-in management list, running the plug-in initialization script;

[0162] Calling the plug-in interface script through the plug-in initialization script, and displaying the main interface corresponding to the first target plug-in according to the plug-in interface script;

[0163] In response to a triggering operation on a target function control in a main interface corresponding to the first target plug-in, running the plug-in startup script;

[0164] The plug-in function logic script is called through the plug-in startup script, and the target function logic script corresponding to the target function control is run according to the plug-in function logic script.

[0165] In an optional implementation, the plug-in management interface further includes: setting controls, and the method further includes:

[0166] In response to a triggering operation on the setting control, the plug-in management list and / or the display style of each plug-in label in the plug-in management list are adjusted, wherein the display style includes a display font and / or a display color.

[0167] In an optional implementation manner, the plug-in management interface further includes: hiding the display control, and the method further includes:

[0168] In response to a selection operation on at least some plug-in tags in the plug-in management list, determining plug-in tags to be hidden;

[0169] In response to the triggering operation of the hide display control, the plug-in label to be hidden is undisplayed in the plug-in management list.

[0170] In an optional implementation, the plug-in management interface further includes: adjusting controls, and the method further includes:

[0171] In response to the triggering operation on the adjustment control, the display order of each plug-in label in the plug-in management list is adjusted.

[0172] In an optional implementation, the plug-in management interface further includes: a first update control, and the method further includes:

[0173] In response to the triggering operation on the first update control, scanning the plug-in folder under the preset target path to obtain a scanning result;

[0174] Determining the plug-in tag to be imported according to the scanning result and the historical import record, wherein the historical import record includes the plug-in tag currently displayed in the plug-in management list;

[0175] The plug-in management list is updated according to the plug-in tag to be imported.

[0176] In an optional implementation, the plug-in management interface further includes: a second update control, and the method further includes:

[0177] In response to a selection operation on at least some of the plug-in tags in the plug-in management list, determining plug-in tags to be updated;

[0178] In response to the triggering operation on the second update control, the plug-in folders corresponding to the plug-in tags to be updated are updated according to a preset update path.

[0179] The specific implementation method and technical effects of the above method embodiment are similar to those mentioned above and will not be repeated here.

[0180] Optionally, the present application also provides a computer program product, which includes instructions, and when the instructions are executed on an electronic device, the electronic device implements the steps of the above method embodiment.

[0181] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0182] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0183] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0184] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the methods of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, abbreviated: ROM), random access memory (English: Random Access Memory, abbreviated: RAM), disk or optical disk and other media that can store program codes.

[0185] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0186] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application. It should be noted that similar numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A plug-in management method, characterized in that: The method comprises: In response to a start-up operation of a target application, a main interface corresponding to the target application is displayed, and a plug-in management interface corresponding to a target management plug-in is displayed on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, wherein the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application; In response to a triggering operation on a first target plug-in tag in the plug-in management list, the first target plug-in is started to call a functional logic corresponding to the first target plug-in.

2. The method according to claim 1, characterized in that The displaying of the plug-in management interface corresponding to the target management plug-in on the main interface corresponding to the target application includes: Scan the plugin folder under the preset target path; If the naming of the plug-in folder meets the preset requirements, determining the plug-in tag according to the naming of the plug-in folder; According to the plug-in tag, a plug-in management interface corresponding to the target management plug-in is displayed on the main interface corresponding to the target application.

3. The method according to claim 2, characterized in that The plug-in folder includes the following scripts: a plug-in initialization script, a plug-in startup script, a plug-in function logic script, and a plug-in interface script; in response to the trigger operation on the first target plug-in tag in the plug-in management list, starting the first target plug-in to call the function logic corresponding to the first target plug-in includes: In response to a trigger operation on a first target plug-in tag in the plug-in management list, running the plug-in initialization script; Calling the plug-in interface script through the plug-in initialization script, and displaying the main interface corresponding to the first target plug-in according to the plug-in interface script; In response to a triggering operation on a target function control in a main interface corresponding to the first target plug-in, running the plug-in startup script; The plug-in function logic script is called through the plug-in startup script, and the target function logic script corresponding to the target function control is run according to the plug-in function logic script.

4. The method according to claim 1, characterized in that: The plug-in management interface further includes: setting controls, and the method further includes: In response to a triggering operation on the setting control, the plug-in management list and / or the display style of each plug-in label in the plug-in management list are adjusted, wherein the display style includes a display font and / or a display color.

5. The method according to claim 1, characterized in that The plug-in management interface further includes: hiding the display control, and the method further includes: In response to a selection operation on at least some plug-in tags in the plug-in management list, determining plug-in tags to be hidden; In response to the triggering operation of the hide display control, the plug-in label to be hidden is undisplayed in the plug-in management list.

6. The method according to any one of claims 1 to 5, characterized in that: The plug-in management interface further includes: adjusting controls, and the method further includes: In response to the triggering operation on the adjustment control, the display order of each plug-in label in the plug-in management list is adjusted.

7. The method according to claim 2, characterized in that The plug-in management interface further includes: a first update control, and the method further includes: In response to the triggering operation on the first update control, scanning the plug-in folder under the preset target path to obtain a scanning result; Determining the plug-in tag to be imported according to the scanning result and the historical import record, wherein the historical import record includes the plug-in tag currently displayed in the plug-in management list; The plug-in management list is updated according to the plug-in tag to be imported.

8. The method according to claim 2, characterized in that: The plug-in management interface further includes: a second update control, and the method further includes: In response to a selection operation on at least some of the plug-in tags in the plug-in management list, determining plug-in tags to be updated; In response to the triggering operation on the second update control, the plug-in folders corresponding to the plug-in tags to be updated are updated according to a preset update path.

9. A plug-in management device, characterized in that: include: A display module is used to display a main interface corresponding to the target application in response to a start operation of the target application, and to display a plug-in management interface corresponding to the target management plug-in on the main interface corresponding to the target application, wherein the plug-in management interface includes: a plug-in management list, wherein the plug-in management list displays a plug-in label of at least one other plug-in connected to the target application; The startup module is used to start the first target plug-in in response to the trigger operation of the first target plug-in tag in the plug-in management list to call the functional logic corresponding to the first target plug-in.

10. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the storage medium communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of the plug-in management method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the plug-in management method according to any one of claims 1 to 8 are executed.

Images